Bug 1551646

Summary: MetricsCollectorWorker exceeds memory
Product: Red Hat CloudForms Management Engine Reporter: Niladri Roy <niroy>
Component: PerformanceAssignee: Keenan Brock <kbrock>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: high    
Version: 5.7.0CC: cpelland, dmetzger, kbrock, nchugh, niroy, obarenbo
Target Milestone: GA   
Target Release: 5.8.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-21 17:14:39 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:

Description Niladri Roy 2018-03-05 15:51:30 UTC
Description of problem:
Metrics collector worker repeatedly exceeded memory

Version-Release number of selected component (if applicable):
5.7.4.2

How reproducible:
everytime at Customer's env

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Keenan Brock 2018-03-07 01:26:28 UTC
Hi Niladri,

I went through the logs. It doesn't look like it was cycling the workerse
The logs were for 24 hours and there were not an excessive number of collectors (or any worker for that matter.

What exactly is your problem?
--Keenan

Comment 4 Niladri Roy 2018-03-07 07:48:00 UTC
Keenan,

The primary issue is Customer is unable to run a specific chargeback report, it gets stuck in a "generating report" state

While analysing the logs we see that the metrics collector worker, even set at it's max limit (1.5 GB) crosses the memory limit, would this be a possibility of a memory leak ?

Would this affect the report generation by making the system run out of memory?

Comment 5 dmetzger 2018-03-07 13:48:10 UTC
Niladri, can you provide an archive log set for this machine?

Comment 14 dmetzger 2018-03-21 17:14:39 UTC
Hot fix is available to resolve the memory leak, see https://bugzilla.redhat.com/show_bug.cgi?id=1536692

*** This bug has been marked as a duplicate of bug 1536692 ***