Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 1 Jul 2016 15:30:11 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12986217.1467386958000.5626.1467387011116@Atlassian.JIRA>
In-Reply-To: <JIRA.12986217.1467386958000@Atlassian.JIRA>
References: <JIRA.12986217.1467386958000@Atlassian.JIRA> <JIRA.12986217.1467386958465@arcas>
Subject: [jira] [Created] (AMBARI-17527) Setup logging to find memory leak
 rootcause
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 01 Jul 2016 15:30:13 -0000

Andrew Onischuk created AMBARI-17527:
----------------------------------------

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