Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1289960[details]
Patch for more effective refreshing of remote execution commands
Description of problem:
Due to inefficiency of the refreshing of execution, smart_proxy_dynflow_core can
get under heavy CPU load, which can eventually lead to slow response times
and bloated queues.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. run remote execution job against 1000 hosts
Actual results:
smart_proxy_dynflow_core getting to 100% CPU soon, response times
on smart_proxy getting to tens of seconds
Expected results:
Moderate CPU load, fast reponse times on smart-proxy (below second)
Additional info:
Extracted from https://bugzilla.redhat.com/show_bug.cgi?id=1416542#c36 to have more clarity on different parts of the bug.
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