volcano icon indicating copy to clipboard operation
volcano copied to clipboard

The differences of PriorityClass between volcano and default scheduler?

Open zhucan opened this issue 1 year ago • 4 comments

Please provide an in-depth description of the question you have:

for k8s default scheduler: An example use case is for data science workloads. A user may submit a job that they want to be prioritized above other workloads, but do not wish to discard existing work by preempting running pods. The high priority job with preemptionPolicy: Never will be scheduled ahead of other queued pods, as soon as sufficient cluster resources "naturally" become free.

but I don't know clear about the volcano.

What do you think about this question?: if the preemptionPolicy is Never, the high priority jobs will be scheduler always before the low priority jobs or normal jobs?

Environment:

  • Volcano Version:
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

zhucan avatar Jun 04 '24 09:06 zhucan

The priorityClass in volcano also play a role in scheduling and preemption,and job with higher priority can preempt lower job,and also schedule first before lower priority job,but a little difference is that volcano will also consider job's queue priority.

Monokaix avatar Jun 05 '24 06:06 Monokaix

so, The high priority job with "preemptionPolicy: Never" will not be scheduled ahead of other queued pods? @Monokaix

zhucan avatar Jun 05 '24 07:06 zhucan

so, The high priority job with "preemptionPolicy: Never" will not be scheduled ahead of other queued pods? @Monokaix

It depends, queue's order is determined by share value, if a queue has a lower share value, jobs in this queue will schedule first. Refer to https://volcano.sh/zh/docs/v1-8-2/plugins/#drf for more detail.

Monokaix avatar Jun 05 '24 07:06 Monokaix

@zhucan Right now volcano hasn't support preemptionPolicy yet, we prepare to implement it, see this: #3642

JesseStutler avatar Sep 19 '24 06:09 JesseStutler

Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

stale[bot] avatar Feb 01 '25 01:02 stale[bot]

Closing for now as there was no activity for last 90 days after marked as stale, let us know if you need this to be reopened! 🤗

stale[bot] avatar May 06 '25 02:05 stale[bot]