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.
Description of problem:
According to the pulp documentation, the pulp workers do not release all of the memory once all of the tasks are completed. The workaround for the issue was suggested to be, set the PULP_MAX_TASKS_PER_WORKER to allow recycling the workers once they process a certain number of tasks.
This setting PULP_MAX_TASKS_PER_WORKER was enabled and set to a value of 2 in the 6.2 but seems to be disabled with Satellite 6.3
Can it be possibly enabled again in the Satellite 6.3 Release
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 1Tanya Tereshchenko
2017-08-01 15:07:56 UTC
Default for PULP_MAX_TASKS_PER_WORKER is not configured on the Pulp component side I think.
Feel free to change component if I guessed it wrong
Comment 5Satellite Program
2017-08-10 14:05:26 UTC
Checked on Satellite 6.3 Snap 17 (katello-3.4.5-3.el7sat, foreman-1.15.4.1-1.el7sat). PULP_MAX_TASKS_PER_CHILD is set to 2 in the default config.
$ cat /etc/default/pulp_workers
# Configuration file for Pulp's Celery workers
# Define the number of worker nodes you wish to have here. This defaults to the number of processors
# that are detected on the system if left commented here.
PULP_CONCURRENCY=8
# Configure Python's encoding for writing all logs, stdout and stderr
PYTHONIOENCODING="UTF-8"
# To avoid memory leaks, Pulp can terminate and replace a worker after processing X tasks. If
# left commented, process recycling is disabled. PULP_MAX_TASKS_PER_CHILD must be > 0.
PULP_MAX_TASKS_PER_CHILD=2
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