-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Reclaim: Have the ability to rank victim nodes based on what's running in them #3997
Comments
This is a useful question that needs to be enhanced in v1.12 or in the patch version of v1.11, we can filter through all the victims first and then prioritize them accordingly |
cc @Monokaix, this should be planned for v1.12 milestone? |
Btw, we experienced a similar issue with preemption in where it didn't have context of what was running in the nodes. I'm just adding a comment here in case the solutions are the same. This is what we tried to fix here #3960 but there may be a better fix than that. |
In preempt action? |
Correct. |
Something that might be useful here too is if we allow reclaim to not happen after scoring the nodes and finding out that all jobs are gang jobs. |
What is the problem you're trying to solve
A follow to this thread: https://cloud-native.slack.com/archives/C011GJDQS0N/p1738726065356349?thread_ts=1738361347.510989&cid=C011GJDQS0N
Reclaim goes note by node without having any ranking function in terms of what's running in them. Is there a way to rank the nodes based on what's running in them. For example if tasks from jobs that are in lower priority queues?
Describe the solution you'd like
For example before running this: https://github.com/volcano-sh/volcano/blob/master/pkg/scheduler/actions/reclaim/reclaim.go#L141
Could we rank the nodes in a certain order?
Thanks!
Additional context
No response
The text was updated successfully, but these errors were encountered: