scheduler: prevent -Inf in job anti affinity scoring #18039
Closed
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.
Similar to #17198, we are seeing
I am yet able to replicate the issue. My understanding is that with desiredCount of
0
, there should be no allocation placement, hence no ranking/feasibility code should run.nomad/scheduler/generic_sched.go
Lines 454 to 469 in 13ee343
That being said, it is happening and I believe the fix is straightforward.
I'll update the PR with more unit tests if possible once we understood the root cause.