[jira] [Commented] (AMBARI-17527) Setup logging to find memory leak rootcause

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359406#comment-15359406 ] 

Hudson commented on AMBARI-17527:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5203 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5203/])
AMBARI-17527. Setup logging to find memory leak rootcause (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dfd1ce49234b935cfb73f3a7c1b3fd558d2fe5b8])
* ambari-agent/src/main/python/ambari_agent/main.py


> 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)