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

drivers/exec: Don't inherit Nomad oom_score_adj value #10698

Merged
merged 2 commits into from
Jun 3, 2021

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Jun 3, 2021

Explicitly set the oom_score_adj value for exec and java tasks.

We recommend that the Nomad service to have oom_score_adj of a low value
(e.g. -1000) to avoid having nomad agent OOM Killed if the node is
oversubscriped.

However, Nomad's workloads should not inherit Nomad's process, which is
the default behavior.

Added a failed test first that you can see in https://app.circleci.com/pipelines/github/hashicorp/nomad/16419/workflows/2c6fee1f-13c5-4d8b-99c2-75bce52bb949/jobs/158264 .

Fixes #10663

Mahmood Ali added 2 commits June 3, 2021 13:18
Explicitly set the `oom_score_adj` value for `exec` and `java` tasks.

We recommend that the Nomad service to have oom_score_adj of a low value
(e.g. -1000) to avoid having nomad agent OOM Killed if the node is
oversubscriped.

However, Nomad's workloads should not inherit Nomad's process, which is
the default behavior.
@notnoop notnoop added this to the 1.1.1 milestone Jun 3, 2021
@notnoop notnoop requested a review from shoenig June 3, 2021 17:28
@notnoop notnoop self-assigned this Jun 3, 2021
@notnoop notnoop added this to Needs Triage in Nomad - Community Issues Triage via automation Jun 3, 2021
@notnoop notnoop changed the title B exec oom score adj drivers/exec: Don't inherit Nomad oom_score_adj value Jun 3, 2021
Copy link
Member

@shoenig shoenig left a comment

Choose a reason for hiding this comment

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

LGTM!

@notnoop notnoop merged commit 0be58d7 into main Jun 3, 2021
Nomad - Community Issues Triage automation moved this from Needs Triage to Done Jun 3, 2021
@notnoop notnoop deleted the b-exec-oom-score-adj branch June 3, 2021 18:15
notnoop pushed a commit that referenced this pull request Jun 9, 2021
Explicitly set the `oom_score_adj` value for `exec` and `java` tasks.

We recommend that the Nomad service to have oom_score_adj of a low value
(e.g. -1000) to avoid having nomad agent OOM Killed if the node is
oversubscriped.

However, Nomad's workloads should not inherit Nomad's process, which is
the default behavior.

Fixes #10663
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exec/Java: Default OOMScoreAdjust causes memory limit to be ignored
3 participants