-
Notifications
You must be signed in to change notification settings - Fork 152
fix: exclude Releasing pods from max pods predicate count #964
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
Open
itsomri
wants to merge
1
commit into
main
Choose a base branch
from
fix/max-pods-exclude-releasing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes a bug where the max pods predicate incorrectly counted pods in Releasing state (being preempted/evicted) toward the node's max pod limit, preventing new pods from scheduling even when slots were freeing up. Solution: Added AllocatedPodCount field to NodeInfo that tracks only actively allocated pods (excludes Releasing). This provides O(1) access with no map lookups or event handler overhead. - Added NodeInfo.AllocatedPodCount field - Incremented in AddTask for actively allocated pods - Decremented in RemoveTask for actively allocated pods - Updated max pods predicate to use AllocatedPodCount - Added unit test for preemption scenario with 110 pods - Updated all test expectations to validate AllocatedPodCount Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
📊 Performance Benchmark ResultsComparing PR ( Legend
Raw benchmark dataPR branch: Main branch: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This fixes a bug where the max pods predicate incorrectly counted pods in Releasing state (being preempted/evicted) toward the node's max pod limit, preventing new pods from scheduling even when slots were freeing up.
Checklist