-
Notifications
You must be signed in to change notification settings - Fork 44
Open
Description
I am seeing an issue with task priority in the following setup:
hq v0.25.0(built from source)- multiple running hq workers
- multiple jobs with tasks that have no explicit priority set (default to zero - validated via
hq task infoto have priority==0) - multiple jobs where all tasks have priority -5
- a new job is submitted where all tasks have priority -1 (validated via
hq task info)
(all jobs submitted via JDF)
The issue is that the job in (5) ends up being allocated almost all of the worker resources while thousands of runnable tasks in (3), that hq sees as having higher priority, are in the WAITING state. Somehow the job being submitted last with all of its tasks having priority -1 has jumped the queue of priority 0 tasks.
I have not used the priority feature much, but I have used it occasionally prior to upgrading to v0.25.0 and did not notice this issue before.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels