Bug 1511859 - Possible Memory Leak in MetricsCollector Worker
Summary: Possible Memory Leak in MetricsCollector Worker
Keywords:
Status: CLOSED DUPLICATE of bug 1535720
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Performance
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.0
Assignee: Keenan Brock
QA Contact: Dave Johnson
URL:
Whiteboard: testathon
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-10 10:15 UTC by Himanshu Roy
Modified: 2018-02-23 14:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-23 13:42:19 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Comparison of leak rate between 5.8 and 5.9 over a 4 day period. (117.62 KB, application/pdf)
2018-01-15 15:27 UTC, dmetzger 		no flags Details
View All

Comment 7 dmetzger 2018-01-15 15:27:48 UTC 
Created attachment 1381554 [details]
Comparison of leak rate between 5.8 and 5.9 over a 4 day period.
Comment 8 Keenan Brock 2018-01-19 18:24:06 UTC 
A possible fix has been proposed in this related BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1535720


That is targeted for the MiqServer, and high confidence that it will fix the leak there.  Updates will probably happen there more regularly until we determine if there is a different leak in the MetricsCollectorWorker, and there is a high probability this was a leak across all workers.
Comment 9 Keenan Brock 2018-02-07 13:47:00 UTC 
Hello Himanshu,

Would you double check the latest code to see if this is still an issue?

Thanks
Keenan
Comment 11 dmetzger 2018-02-23 13:42:19 UTC 
This leak was associated with a Ruby "require" leak which was identified in the Miq Server and has been fixed under the master https://bugzilla.redhat.com/show_bug.cgi?id=1535720

*** This bug has been marked as a duplicate of bug 1535720 ***
Note You need to log in before you can comment on or make changes to this bug.