Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Jul 2016 20:49:11 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12987923.1468010931000.61996.1468010951023@Atlassian.JIRA>
In-Reply-To: <JIRA.12987923.1468010931000@Atlassian.JIRA>
References: <JIRA.12987923.1468010931000@Atlassian.JIRA> <JIRA.12987923.1468010931550@arcas>
Subject: [jira] [Created] (YARN-5341) Nodemanager leaks ContainerResource
 names in UniqueNames for each container
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 08 Jul 2016 20:52:07 -0000

Jason Lowe created YARN-5341:
--------------------------------

             Summary: Nodemanager leaks ContainerResource names in UniqueNames for each container
                 Key: YARN-5341
                 URL: https://issues.apache.org/jira/browse/YARN-5341
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
    Affects Versions: 2.7.2
            Reporter: Jason Lowe
            Priority: Critical


Ran across a nodemanager that was spending most of its time in GC.  Upon examination of the heap most of the memory was going to the map of names in org.apache.hadoop.metrics2.lib.UniqueNames.  In this case the map had almost 2 million entries.  Looking at a few of the map showed entries like "ContainerResource_container_e01_1459548490386_8560138_01_002020", "ContainerResource_container_e01_1459548490386_2378745_01_000410", etc.

Looks like the ContainerMetrics for each container will cause a unique name to be registered with UniqueNames and the name will never be unregistered.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org