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

Backport of core: emit node evals only for sys jobs in dc into release/1.3.x #13628

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #12955 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

The below text is copied from the body of the original PR.


Whenever a node joins the cluster, either for the first time or after
being down, we emit a evaluation for every system job to ensure all
applicable system jobs are running on the node.

This patch adds an optimization to skip creating evaluations for system
jobs not in the current node's DC. While the scheduler performs the same
feasability check, skipping the creation of the evaluation altogether
saves disk, network, and memory.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/f-skip-eval-on-dc/terribly-better-adder branch from d5f42f4 to 6acc90b Compare July 6, 2022 21:35
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 701cd78 into release/1.3.x Jul 6, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/f-skip-eval-on-dc/terribly-better-adder branch July 6, 2022 21:35
@github-actions
Copy link

github-actions bot commented Nov 4, 2022

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 4, 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.

None yet

2 participants