Bug 1890916

Summary: Pulp worker can consume high memory when publishing a repository with large metadata files
Product: Red Hat Satellite Reporter: James Jeffers <jjeffers>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: ahumbe, bbuckingham, bmbouter, dgross, dkliban, ggainey, hyu, ipanova, jsherril, ldelouw, mmccune, pcreech, rchan, satellite6-bugs, ttereshc, vsedmik, wclark, zhunting
Target Milestone: 6.8.1Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pulp-rpm-2.21.3.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1876782 Environment:
Last Closed: 2020-11-23 17:13:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 James Jeffers 2020-10-23 10:04:33 UTC
*** Bug 1890917 has been marked as a duplicate of this bug. ***

Comment 9 Lai 2020-11-18 15:48:36 UTC
Steps to retest:

1. Set Pulp to use only 1 worker so that we can monitor the progress easily.  This can be done by modifying pulp_concurrancy=1 in /etc/default/pulp_workers
2. Restart pulp_workers: systemctl restart pulp_workers
3. Enable and sync rhel-7-server-rpms
4. Use the following command to monitor the memory usage.

watch 'ps -aux | grep reserved_resource_worker-0'

5. Create cv and add rhel-7-server-rpms
6. Publish cv
7. Monitor pulp worker from step 3

Expected:
Processing should not reach 3GB

Actual:
Processing took up to 1.3GB as highest memory consumption that I've seen.  It stabilizes around 1GB. 

Since we're below the threshold of 3GB, this is verified.

Verified on 6.8.1_snap 2

Checked pulp version on system as pulp-rpm-plugins-2.21.3.1-1.el7sat.noarch

Comment 13 errata-xmlrpc 2020-11-23 17:13:53 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 (Satellite 6.8.1 Async Bug Fix Update), 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/RHBA-2020:5180

Comment 14 Mike McCune 2020-11-25 16:47:11 UTC
*** Bug 1899312 has been marked as a duplicate of this bug. ***