Bug #24435
closedThe dynflow scheduling mechanism can lead to tasks initiated later to be executed sooner, leaving older tasks waiting
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1609371
Description of problem:
Due to original dynflow scheduling, some tasks can be discriminated in favour of newer tasks when under heavy load: even though the overall execution takes overaly the same amount, there are higher spikes on longer-running tasks.
Version-Release number of selected component (if applicable):
How reproducible:
requires special setup to observer reliably
Steps to Reproduce:
1. trigger a lot (200+) of small execution plans (applicability on large amount hosts is a good example)
2. watch task duration of the tasks
Actual results:
some tasks finish relatively fast, while others wait unexpectedly long to finish: newer tasks of the same type get finished much sooner, than other older tasks.
Expected results:
FIFO: tasks triggered sooner should finish sooner, than newer tasks of the same type and complexity.