Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable the LSF plm if CSM is detected #4439

Merged
merged 1 commit into from
Nov 29, 2017
Merged

Conversation

mattaezell
Copy link
Contributor

LSF running on top of CSM does not provide LSF daemons on the compute nodes. Attempts to run will result in errors like:

Nov  2 16:47:03 2017 120499 7 10.1 lsb_pjob_res_connect: lsb_pjob_connect_to_res(compute01) failed.

LSF running on top of CSM does not provide LSF daemons on the compute nodes.

Signed-off-by: Matt Ezell <ezellma@ornl.gov>
@ompiteam-bot
Copy link

Can one of the admins verify this patch?

@mattaezell
Copy link
Contributor Author

Are you OK with this change @jjhursey and @dsolt ?

@jsquyres
Copy link
Member

jsquyres commented Nov 2, 2017

ok to test

@jjhursey
Copy link
Member

Sorry this got lost in the run up to SC. I'll try to get to it early this week. Sorry for the delay.

Copy link
Member

@jjhursey jjhursey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good. Thanks!

There are some environments/setups where the CSM_ALLOCATION_ID might be set, but LSF can still be used to launch. However, there is no good way of detecting that scenario at the moment. We will work on a way to better detect that in a future PR.

@jjhursey jjhursey removed the request for review from dsolt November 29, 2017 13:42
@jjhursey jjhursey merged commit 38aefd2 into open-mpi:master Nov 29, 2017
@jjhursey
Copy link
Member

@mattaezell Do you want this change in the three release branches (v2.x, v3.0.x, v3.1.x) as well?

@mattaezell mattaezell deleted the lsf_csm branch November 29, 2017 14:49
@mattaezell
Copy link
Contributor Author

Thanks @jjhursey. I'm not sure exactly what versions people are testing with here locally, let me check.

@jjhursey
Copy link
Member

@mattaezell I filed PRs to take this to the v3.0.x and v3.1.x series. Sorry for the delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants