Project

General

Profile

Actions

Bug #19061

closed

uploading facts involves synchronous dynflow task, can cause bottleneck

Added by Marek Hulán about 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1435370

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.

Actions

Also available in: Atom PDF