Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691416 - Delays when many clients upload tracer data simultaneously
Summary: Delays when many clients upload tracer data simultaneously
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: katello-tracer
Version: 6.3.5
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Perry Gagne
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-21 14:54 UTC by Brian Smith
Modified: 2019-03-27 03:01 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Brian Smith 2019-03-21 14:54:31 UTC
Description of problem:
When customer patches around 60 servers simultaneously from Satellite, many of them get to the "Uploading Tracer Profile" step around the same time, and some clients have delays of over 15 minutes.  It is also possible to reproduce this by running a remote execution "katello-tracer-upload" command on multiple hosts.  

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

How reproducible:  Consistently

Steps to Reproduce:
1.  Have around 160 Satellite clients with katello-host-tools-tracer installed.
2.  Create a Remote Execution job to run on the 160 clients and run the command "time katello-tracer-upload", with a 15 minute time out.

Actual results:  In customers environment, 3 of the servers timed out after 15 minutes, and 2 servers ran for over 5 minutes.  

Expected results:  Servers not taking over 15 minutes to run katello-host-tools-tracer

Additional info:
Customer ran the same Remote execution job, but set the concurrency level to 1, so that it only ran on one server at a time, and did not have any failures or delays.   

See also:

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