Bug 1463801

Summary: qpid dispatch router on capsule leaking memory at scale
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: PerformanceAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.0CC: alexandre.chanu, arcsharm, bkearney, cduryee, dcaplan, egolov, inecas, jcallaha, jentrena, jhutar, mcressma, mmccune, omaciel, pmoravec, psuriset, tross
Target Milestone: UnspecifiedKeywords: Performance, PrioBumpPM, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: scale_lab
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1368718 Environment:
Last Closed: 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 2 jcallaha 2017-10-18 19:55:16 UTC 
Verified in Satellite 6.3 Snap 20.

I ran the loop, outlined in https://bugzilla.redhat.com/show_bug.cgi?id=1368718#c12, on 100 hosts. At no point did the memory leak present itself. 

Before
------
qpidd    32415  0.7  0.0 498176 32724 ?        Ssl  13:45   0:04 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf

During
------
qpidd    32415  1.1  0.1 522908 40836 ?        Ssl  13:45   0:12 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
qpidd    32415  1.3  0.1 546440 48984 ?        Ssl  13:45   0:18 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
qpidd    32415  1.5  0.1 550352 52696 ?        Ssl  13:45   0:25 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
qpidd    32415  2.2  0.2 550012 67224 ?        Ssl  13:45   1:24 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf

After
-----
qpidd    32415  2.2  0.2 548156 67688 ?        Ssl  13:45   1:25 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
qpidd    32415  1.9  0.1 501428 57268 ?        Ssl  13:45   1:35 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
Comment 3 Bryan Kearney 2018-02-21 17:33:25 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, 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
Comment 4 Bryan Kearney 2018-02-21 17:33:45 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, 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