Skip to content
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

Scheduling only priority pods while there are priority pods in the queue #3832

Open
netang opened this issue Nov 20, 2024 · 2 comments
Open
Labels
kind/question Categorizes issue related to a new question

Comments

@netang
Copy link

netang commented Nov 20, 2024

Please describe your problem in detail

Is it possible to run Spark applications (on Kubernetes) using Volcano so that only high-priority pods are scheduled first and low-priority pods wait until all high-priority pods are scheduled?

Any other relevant information

When I run Spark applications using the default Kubernetes scheduler, I get situations where "small" pods with low priority are scheduled before pods with high priority (https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#effect-of-pod-priority-on-scheduling-order). So I started looking towards Volcano.

@netang netang added the kind/question Categorizes issue related to a new question label Nov 20, 2024
@JesseStutler
Copy link
Member

Yes, volcano can, high-priority pods will pop from queue before the low-priority pods, but you may have to specify them in the same queue.

@netang
Copy link
Author

netang commented Nov 21, 2024

Yes, volcano can, high-priority pods will pop from queue before the low-priority pods, but you may have to specify them in the same queue.

Even if priority pods cannot be scheduled at the moment (they lack resources), but non-priority pods can (they have enough resources)? Will low priority pods wait in this case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Categorizes issue related to a new question
Projects
None yet
Development

No branches or pull requests

2 participants