Disable immediate allocation for NP jobs #114
Merged
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.
_allocate_one
looks at existing pods to look for an available node for the newly-added job. There could be a situation where two consecutive non-preemptible jobs can both get the same allocation because the earlier job haven't spawned any replica pods yet. This can trigger a reallocation for the second non-preemptible job at a later full allocation cycle which crashes the allocator because it violates the basic assumption about pinned non-preemptible jobs. This fix only allows this optimization for preemptible jobs.