Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1101717

Summary: celery process consuming a lot of memory after running for few days with provisioning configured
Product: [Retired] Pulp Reporter: Michael Hrivnak <mhrivnak>
Component: async/tasksAssignee: Brian Bouterse <bmbouter>
Status: CLOSED CURRENTRELEASE QA Contact: Preethi Thomas <pthomas>
Severity: high Docs Contact:
Priority: high    
Version: 2.4 BetaCC: jhutar, pthomas
Target Milestone: ---Keywords: Triaged
Target Release: 2.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1101142 Environment:
Last Closed: 2014-08-09 06:55:25 UTC Type: Bug
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:    
Bug Blocks: 1101142    

Comment 1 Michael Hrivnak 2014-05-27 19:16:16 UTC
I was able to reproduce this and determine that qpid.messaging holds a copy of each message received until that message gets acked. If you don't ack them, which celery often does not, they just pile up indefinitely.

Brian had already submitted a PR that fixes this issue: https://github.com/pulp/kombu/pull/6

Comment 2 Brian Bouterse 2014-05-28 15:11:29 UTC
PR available at:

https://github.com/pulp/pulp/pull/988

Comment 3 Brian Bouterse 2014-05-28 15:11:46 UTC
Merged

Comment 4 Randy Barlow 2014-05-29 18:07:27 UTC
This was fixed in pulp-2.4.0-0.19.beta.

Comment 5 Michael Hrivnak 2014-07-03 19:23:40 UTC
This can be verified by watching pulp run for a period of time and observing that the memory consumption of worker processes does not grow steadily.

Comment 6 Preethi Thomas 2014-07-07 10:14:55 UTC
I have had the pulp-server running for a few days and have not seen any major change in memory consumption.

Moving to verified

Comment 7 Randy Barlow 2014-08-09 06:55:25 UTC
This has been fixed in Pulp 2.4.0-1.