Red Hat Bugzilla – Bug 1465296
It takes too long for parent task to stop after its sub-tasks have stopped
Last modified: 2018-02-21 11:54:37 EST
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):
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)
Parent task keeps running for hours after its sub-tasks have stopped
The parent task is stopped shortly after its sub-tasks have stopped
Created redmine issue http://projects.theforeman.org/issues/20114 from this bug
Align to 6.3+ please: the upstream release, compatible with 1.15 will come after the the tasks dependency gets in https://github.com/theforeman/foreman-packaging/pull/1822
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > For information on the advisory, and where to find the updated files, follow the link below.
> > If the solution does not work for you, open a new bug report.
> > https://access.redhat.com/errata/RHSA-2018:0336