Bug 1435370 - uploading facts involves synchronous dynflow task, can cause bottleneck
Summary: uploading facts involves synchronous dynflow task, can cause bottleneck
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Fact
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Chris Duryee
QA Contact: Peter Ondrejka
Depends On:
Blocks: 1353215
TreeView+ depends on / blocked
Reported: 2017-03-23 15:53 UTC by Chris Duryee
Modified: 2020-08-13 08:59 UTC (History)
10 users (show)

Fixed In Version: rubygem-katello-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1446710 (view as bug list)
Last Closed: 2017-06-20 17:23:29 UTC
Target Upstream Version:

Attachments (Terms of Use)
proposed patch to make host update async on fact upload (657 bytes, patch)
2017-03-23 15:54 UTC, Chris Duryee
no flags Details | Diff

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19061 0 High Closed uploading facts involves synchronous dynflow task, can cause bottleneck 2020-07-16 12:05:15 UTC
Red Hat Product Errata RHBA-2017:1553 0 normal SHIPPED_LIVE Satellite 6.2.10 Async Bug Release 2017-06-20 21:19:07 UTC

Description Chris Duryee 2017-03-23 15:53:31 UTC
Description of problem:

If a Satellite server is heavily loaded and has lots of tasks queued, you may start to see the web UI and API become unresponsive. Many of the passenger workers will be hung waiting on URLs like this:

PUT /rhsm/consumers/<UUID>

The root cause is that updating facts kicks off a synchronous dynflow task. If dynflow is backed up, client fact uploads will get slower and slower, eventually consuming all passenger workers.

Version-Release number of selected component (if applicable): 6.2.8

Steps to Reproduce:
1. create a large number of tasks that have to be run
2. on a registered client, delete /var/lib/rhsm/facts/facts.json and run subscription-manager facts --update

Actual results: slow response, possible timeouts

Expected results: the client should get a reply quickly and the host update can then happen asynchronously. Note that if the async task fails, the client would not be aware.

Comment 1 Chris Duryee 2017-03-23 15:54:13 UTC
Created attachment 1265824 [details]
proposed patch to make host update async on fact upload

Comment 3 Marek Hulan 2017-03-29 07:52:28 UTC
Created redmine issue http://projects.theforeman.org/issues/19061 from this bug

Comment 5 Satellite Program 2017-03-29 18:15:18 UTC
Upstream bug assigned to cduryee

Comment 6 Satellite Program 2017-04-05 18:15:36 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19061 has been resolved.

Comment 8 Peter Ondrejka 2017-05-26 11:43:23 UTC
Verified in satellite-6.2.10-1.0.el7sat.noarch, updating facts while running a remote job on 3000 hosts was done asynchronously without delay

Comment 12 errata-xmlrpc 2017-06-20 17:23:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.