SCHED-957: OOM killer should kill docker containers before slurmd#2319
Draft
SCHED-957: OOM killer should kill docker containers before slurmd#2319
Conversation
faucct
force-pushed
the
feature/SCHED-957-oom-killer-should-kill-docker-containers-before-slurmd
branch
2 times, most recently
from
4e35d12 to
be3155a
Compare
faucct
force-pushed
the
feature/SCHED-957-oom-killer-should-kill-docker-containers-before-slurmd
branch
from
be3155a to
783a3ba
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
When users spawn memory-heavy processes, e.g. docker containers, the OOM killer can kill slurmd instead of the processes.
Solution
Tuned the OOM killer a bit. Can extend this to other important processes, e.g. supervisord.
Testing
manual
Release Notes
Adjust the slurmd OOM score to be lower than the one of users' jobs.