Bug #20114
closedIt takes too long for parent task to stop after its sub-tasks have stopped
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1465296
Description of problem:
Bulk tasks are receiving events when their sub-tasks finish. This gets rather slow with large number of sub-tasks. We should take another approach and make the parent task poll the state of its sub-tasks.
Version-Release number of selected component (if applicable):
How reproducible:
Easily triggered by using REX at scale
Steps to Reproduce:
1. Run a remote execution job on high number (thousands) of hosts
2. Wait until all of its sub-tasks are stopped
3. It may reach into state where all the sub-tasks are stopped but the parent task is still running for another hour or so (depends on numbers of hosts)
Actual results:
Parent task keeps running for hours after its sub-tasks have stopped
Expected results:
The parent task is stopped shortly after its sub-tasks have stopped
Additional info:
Updated by Adam Ruzicka over 7 years ago
- Category set to Dynflow
- Target version set to 113
Updated by Ivan Necas over 7 years ago
- Related to Refactor #20466: Use the polling sub plans functionality in RunHostsJob added
Updated by Ivan Necas over 7 years ago
- Status changed from New to Closed
Marking as resolved, as this should be fixed by #20466