-
Notifications
You must be signed in to change notification settings - Fork 984
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
Preemption not working properly for high priority job #2034
Comments
@vincentlau0493 Thanks for your reporting. We have added it in pipeline and take a look as soon as possible. |
#1772 |
Yes, I read that issue, it seems like the problem hasn't been solved, right? I expect the running job would be evicted when high priority job needs resource, but it is not working as my expection. Did I configure anything wrong? |
No, this issue has not been resolved. Just had some discussions, no conclusion yet |
I see. Since my team is going to use this feature, is there any trick to achieve it? I know the low priority pod can be preempted by higher one using native k8s. |
This issue is still under investigation. If there is any new progress, I will reply again. If you have any information that you want to synchronize, please share with us.😀 |
Very much interested in this feature. Premeeting low priority jobs when high priority jobs comes in |
Try this conf:
It works for me now. |
@vincentlau0493 It's not working for me.
Below are low priority jobs,
Below is high priority job,
Pending pogroup details,
Logs,
|
It looks like the podgroup status of vc-job3 is PENDING, however it should be INQUEUE, which means the job was not accepted by queue. Try using one job as low priority sample, and restart the vc scheduler to clear cache. |
@Sharathmk99 |
I've tried with the latest master branch yesterday. It seems that preemption funciton breaks. I'll take some time to take a look at it recently, too. |
There are several ways you could try to make it work depends on you situation:
The principle of 2 and 3 is that both volcano/pkg/scheduler/framework/session_plugins.go Lines 403 to 407 in 42702f7
volcano/pkg/scheduler/framework/session_plugins.go Lines 240 to 243 in 42702f7
The final work config could be:
|
Hello 👋 Looks like there was no activity on this issue for last 90 days. |
Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗 |
What happened:
Low-priority running jobs will not be preempted by pending high-priority jobs when resource is not enough.
What you expected to happen:
Low-priority running job should be evicted and then high priority job starts running.
How to reproduce it (as minimally and precisely as possible):
volcano-scheduler.conf
I created two priority class:
and two jobs with different priority using default queue:
I ran the case on Mac minikube, cpu should be more than 4.
I started with low priority job, the job was running properly. When I created high priority job, the phase of podgroup was stuck at InQueue:
And the pod was pending:
Here is some logs on scheduler:
Anything else we need to know?:
Environment:
kubectl version
): Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:38:26Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"darwin/amd64"}Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:39:34Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
uname -a
): Darwin macdeMacBook-Pro.local 20.5.0 Darwin Kernel Version 20.5.0: Sat May 8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64 x86_64The text was updated successfully, but these errors were encountered: