-
Notifications
You must be signed in to change notification settings - Fork 7.1k
[Core] Update cluster scheduler to handle label selector hard node id constraint #56235
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
Merged
jjyao
merged 15 commits into
ray-project:master
from
ryanaoleary:label-selector-node-id-constraint
Sep 16, 2025
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
16bd8fd
Update scheduler to handle label selector hard node id constraint
ryanaoleary d8226fc
Merge branch 'master' into label-selector-node-id-constraint
ryanaoleary 9ce9890
Fix c++ test
ryanaoleary 0603f0e
Use constants value
ryanaoleary d088786
Remove early failure check
ryanaoleary f08c4c0
Update src/ray/raylet/scheduling/tests/cluster_resource_scheduler_tes…
ryanaoleary 76a1f73
Clarify in comment that this is for infeasible resources
ryanaoleary 0877438
Merge branch 'master' into label-selector-node-id-constraint
ryanaoleary d741f50
Merge branch 'master' into label-selector-node-id-constraint
ryanaoleary 2d29039
Add common:constants dep
ryanaoleary c5bf081
Merge branch 'master' into label-selector-node-id-constraint
MengjinYan e6381e4
Fix imports
ryanaoleary 6b830ca
Merge branch 'master' into label-selector-node-id-constraint
ryanaoleary 4a9bd1f
Merge branch 'master' into label-selector-node-id-constraint
MengjinYan 3e815a2
Merge branch 'master' into label-selector-node-id-constraint
jjyao File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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 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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something we can do smarter in the follow-up is that if we have a list of nodes here, we should pick the node with the most arguments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I'm wondering if the logic should be in here where the core_worker finds the raylet to send the requests to or it should be in the the raylet logic where it finds the best node to send the task?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good question. Currently it has to be here since raylet doesn't have location information of objects (owner does).