[
https://issues.apache.org/jira/browse/AMBARI-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359722#comment-15359722
]
Hudson commented on AMBARI-17527:
-
SUCCESS: Integrated in Ambari-trunk-Commit #5205 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5205/])
AMBARI-17527. Setup logging to find memory leak rootcause (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=148950a2216a84890c9c79d7f44b2436cc78ffc3])
* ambari-agent/src/test/python/resource_management/TestLinkResource.py
* ambari-agent/src/main/python/ambari_agent/main.py
* ambari-agent/src/test/python/resource_management/TestExecuteResource.py
* ambari-agent/src/test/python/ambari_agent/TestCertGeneration.py
* ambari-agent/src/test/python/resource_management/TestDirectoryResource.py
* ambari-agent/src/test/python/ambari_agent/TestShell.py
* ambari-agent/src/test/python/ambari_agent/TestHostname.py
* ambari-agent/src/test/python/ambari_agent/TestHardware.py
* ambari-agent/src/test/python/resource_management/TestDatanodeHelper.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)
