Fix allocation of dead head nodes #794
Merged
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
njbrake
approved these changes
Feb 4, 2025
|
Tracking this issue in https://discuss.ray.io/t/dead-head-nodes-selected-in-scheduling/21686 |
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.
What's changing
When storing the Ray data in Redis, the cluster information goes in as well - including the dead head nodes from previous Ray executions. In some situations, e.g. when a job doesn't have node requirements, the scheduler will place it on the node head, but chances are a dead head node is retrieved.
How to test it
This should avoid error messages mentioning that the assigned node for a job is "infeasible".
Additional notes for reviewers
N/A
I already...
/docs)