You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/07/08 21:07:11 UTC
[jira] [Commented] (YARN-5341) Nodemanager leaks ContainerResource
names in UniqueNames for each container
[ https://issues.apache.org/jira/browse/YARN-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368472#comment-15368472 ]
Jason Lowe commented on YARN-5341:
----------------------------------
Looks like this may be a bug in the metrics system rather than container metrics. At a glance it appears that unregistering a metrics source won't remove the name from UniqueNames which would be a bug in HADOOP rather than YARN if that ends up being the case.
> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org