You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/07/01 15:30:11 UTC
[jira] [Updated] (AMBARI-17527) Setup logging to find memory leak
rootcause
[ https://issues.apache.org/jira/browse/AMBARI-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk updated AMBARI-17527:
-------------------------------------
Attachment: AMBARI-17527.patch
> Setup logging to find memory leak rootcause
> -------------------------------------------
>
> Key: AMBARI-17527
> URL: https://issues.apache.org/jira/browse/AMBARI-17527
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17527.patch
>
>
> We found out that the reason for memory leak is gc being disabled.
> We need to setup logging to figure
> out who and under what circumstances actually disables gc.
> After we do that we can find QE cluster with leak and investigate the
> information.
> This information is essential for fixing the leak.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)