-
Notifications
You must be signed in to change notification settings - Fork 10
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
Environment variable option to disable mpibind #24
Comments
All instructions to launch Flux under Slurm run a single broker per node. Does the Slurm |
We should be able to control this with the Slurm plugin, which is in development. Two options come to mind:
I need to think more about (2), but if it is indeed a reasonable default, then Flux would not have to change anything. |
One idea for 1. would be to use a variable named |
In the case of Flux, we don't want Flux processes to be bound by mpibind when launched under Slurm. Instead, we only want mpibind to be activated once Flux has started. In parts of Flux's documentation, we currently recommend users launch Flux under Slurm with
srun --mpibind=off flux start
, but this only applies to LLNL clusters (open issue).An alternate solution would be to suggest users to do
MPIBIND=off srun flux start
or setMPIBIND=off
in an lmod file, but this requires mpibind to support providing options via environment variables. Once Flux is started, we could unset theMPIBIND
env var when launching jobs (and reactivating mpibind via the Flux mpibind job shell plugin is also an option).The text was updated successfully, but these errors were encountered: