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 scheduler: retain eval metrics on port collision into release/1.6.x #19939

Conversation

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

Backport

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

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


When an allocation can't be placed because of a port collision the resulting blocked eval is expected to have a metric reporting the port that caused the conflict, but this metrics was not being emitted when preemption was enabled.

Closes #19827


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-fix-eval-port-collision/strongly-concrete-toad branch from bc06faf to f8d08b2 Compare February 9, 2024 23:19
@lgfa29 lgfa29 merged commit d4399b2 into release/1.6.x Feb 9, 2024
26 checks passed
@lgfa29 lgfa29 deleted the backport/b-fix-eval-port-collision/strongly-concrete-toad branch February 9, 2024 23:41
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