volcano-sh
:Draft feat: Add dequeue strategies support for queue scheduling
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR introduces dequeue strategies for Volcano queues, allowing administrators to control how jobs are scheduled within queues when resources are limited.
Key Features: Defined DequeueStrategy type with two supported strategies:
-
FIFO Strategy
- The scheduler repeatedly tries to dequeue the first task in the queue.
- If the first task cannot be dequeued (e.g., insufficient resources), it will keep retrying without skipping to the next task.
-
Traversal Strategy
- If the first task cannot be dequeued, the scheduler skips it and attempts to dequeue the next jobs in the queue sequentially.
Which issue(s) this PR fixes:
Fixes #4572 #4690 #3950
Special notes for your reviewer:
- Backward Compatibility: This change is fully backward compatible. Existing queues without dequeue strategy annotations will continue to use the traverse strategy (current default behavior).
Does this PR introduce a user-facing change?
support FIFO dequeue strategies for Volcano queues..
Additional Context:
This feature addresses common scheduling scenarios where different queues require different behavior patterns:
- Production queues often need strict ordering and can tolerate some resource underutilization
- Development/testing queues typically prioritize maximum resource utilization over strict ordering
The implementation uses a unified scheduling loop with conditional logic, making it maintainable and efficient while providing clear behavioral differences between the two strategies.
good feature, I think it's useful, also needed by https://github.com/volcano-sh/volcano/issues/4690
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign wpeng102 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign wpeng102 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Please rebase your codes, BTW,
, just a reminder, when writing commits, please clearly describe the changes made, and avoid vague information such as "fix" or "add crd". @kingeasternsun