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

resources: new oom_score_adj field #23259

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from
Draft

resources: new oom_score_adj field #23259

wants to merge 11 commits into from

Conversation

pkazmierczak
Copy link
Contributor

@pkazmierczak pkazmierczak commented Jun 7, 2024

Adds an oom_score_adj field to resources that only accepts positive values. A task can mark itself as more likely to be OOM killed, but not less likely.

Relates to #11087

Update: After discussing this with @schmichael, we decided to put this PR on hold and implement the feature via driver config for now.

@pkazmierczak pkazmierczak self-assigned this Jun 7, 2024
@pkazmierczak pkazmierczak added backport/ent/1.8.x+ent Changes are backported to 1.8.x+ent backport/1.8.x backport to 1.8.x release line labels Jun 7, 2024
tgross
tgross previously approved these changes Jun 7, 2024
Copy link
Member

@tgross tgross left a comment

Choose a reason for hiding this comment

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

LGTM!

nomad/structs/structs.go Outdated Show resolved Hide resolved
Comment on lines 1 to 3
```release-note:improvement
resources: Added new oom_score_adj field
```
Copy link
Member

Choose a reason for hiding this comment

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

We haven't wired this up to the drivers yet, so if we merge this and end up shipping Nomad 1.8.1 before that work is complete, the changelog entry won't make much sense. Maybe we should hold off adding the changelog entry until all the components (and documentation!) are in place? That way we can safely ship this code in main without stressing about 1.8.1.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i can also remove the backport labels for now.

@pkazmierczak pkazmierczak removed backport/ent/1.8.x+ent Changes are backported to 1.8.x+ent backport/1.8.x backport to 1.8.x release line labels Jun 10, 2024
@pkazmierczak pkazmierczak marked this pull request as draft June 11, 2024 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants