Set MemSpecLimit in slurm.conf and allow configuration using hieradata #181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cmd-ntrf
force-pushed
the
slurm-os-memory
branch
from
d651e8b
to
c2ac18d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Slurm can allocate the entirety of RAM available on a compute node. This can lead to job using all the memory available on a compute node which then leads the oom killer to kill random processes, putting the node in a weird state.
To avoid that, we define a minimum quantity of memory that cannot be allocated by Slurm. To remove the limit, the parameter can be set to 0.