Bug 1463800

Summary:	qpidd consuming huge memory during scale
Product:	Red Hat Satellite	Reporter:	Satellite Program <pm-sat>
Component:	Qpid	Assignee:	Mike Cressman <mcressma>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.2.9	CC:	alexandre.chanu, andrew.schofield, aperotti, arahaman, bbuckingham, bill.scherer, bkearney, brcoca, cduryee, chrobert, codonell, cwelton, dcaplan, dmoessne, egolov, ehelms, gmurthy, hyu, jcallaha, jentrena, jhutar, jortel, jross, jswensso, kabbott, kim.vdriet, mcressma, mhrivnak, mlinden, mmccune, oshtaier, pdwyer, pmoravec, psuriset, sauchter, schamilt, sokeeffe, tross, wpinheir
Target Milestone:	Unspecified	Keywords:	FieldEngineering, Performance, PrioBumpField, PrioBumpPM, Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	scale_lab
Fixed In Version:	qpid-cpp-1.36.0-7	Doc Type:	Bug Fix
Doc Text:	During scaling testing of content hosts, qpid consumed huge amounts of memory. This is now fixed.	Story Points:	---
Clone Of:	1367735	Environment:
Last Closed:	2018-02-21 12:57:54 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:
Bug Depends On:	1450948, 1468450
Bug Blocks:

Comment 6 jcallaha 2018-02-07 15:47:08 UTC

Verified in Satellite 6.3 Snap 31/35.

The tested behavior, in Snap 31, shows an increase of approximately 1MB qpid memory consumption per additional host running katello-agent. Scaling up to 10k hosts, running katello-agent, qpid showed a memory consumption around 10G. This is a 60% drop from the consumption in the initial report!

Additionally, none of our automated or manual tests have shown any breakage from incorporating the new qpid version.

Comment 9 errata-xmlrpc 2018-02-21 12:57:54 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/RHBA-2018:0338