-
Notifications
You must be signed in to change notification settings - Fork 285
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 consumed resources once quit from cohort #1149
Comments
This is somewhat analogous to scheduler vs descheduler. We don't have a process that checks that the decisions taken before still hold. |
Agree, more like a feature. |
I think that this feature request isn't only for RayJob. /retitle Reclaim consumed resources once quit from cohort |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/lifecycle frozen |
What happened:
When clusterQueue quits from the cohort, the resources consumed will not be reclaimed.
cohort-pool
at firstWhat you expected to happen:
high priority rayjob will preempt the lower one.
How to reproduce it (as minimally and precisely as possible):
The process described above.
Anything else we need to know?:
Environment:
kubectl version
):git describe --tags --dirty --always
): maincat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: