You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your proposal:
koord-scheduler supports jobwise preemtption.
Why is this needed:
In a large scale shared-cluster, some quotas may be very busy, some quotas may be idle. If the idle resources can be shared in some way, the resource utilization rate of the cluster will be significantly improved. Moreover, even in one quota, there are some production jobs and develop jobs, user may expect production jobs can preempt develop jobs when resource is busy.
If the pods belongs to a job , we should also consider resource assign\preemption by job level. Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered:
xulinfei1996
changed the title
[proposal] elastic quota plugin suppors jobwise preemption
[proposal] elastic quota plugin support pod-group wise preemption
Jan 15, 2024
xulinfei1996
changed the title
[proposal] elastic quota plugin support pod-group wise preemption
[proposal] elastic quota plugin support job-level oversold management
Jan 15, 2024
eahydra
changed the title
[proposal] elastic quota plugin support job-level oversold management
[proposal] elastic quota plugin support job-level preemption
Jan 30, 2024
What is your proposal:
koord-scheduler supports jobwise preemtption.
Why is this needed:
In a large scale shared-cluster, some quotas may be very busy, some quotas may be idle. If the idle resources can be shared in some way, the resource utilization rate of the cluster will be significantly improved. Moreover, even in one quota, there are some production jobs and develop jobs, user may expect production jobs can preempt develop jobs when resource is busy.
If the pods belongs to a job , we should also consider resource assign\preemption by job level.
Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered: