hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters
Date Tue, 02 Aug 2016 00:58:20 GMT

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

Junping Du commented on HADOOP-13362:
-------------------------------------

bq. 2.7.3 was in lockdown for only critical blockers that were preventing it from being released,
so I just committed it to branch-2.7.
I see. We do see this happen a lot recently in some clusters with enabling container metrics.
So I wish we could have it in 2.7.3.

bq. I'm OK with it going into 2.7.3 if there's still a chance to do so, assuming the 2.7.3
release manager is also OK with it.
Agree. Even this should not block 2.7.3 release, but we should try to get it in if by any
chance. [~vinodkv], I saw you leave comments in 2.7.3-rc0 voting thread that rc0 will be withdrawn.
Can you confirm this patch can be backport to 2.7.3? Thanks!

> DefaultMetricsSystem leaks the source name when a source unregisters
> --------------------------------------------------------------------
>
>                 Key: HADOOP-13362
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13362
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 2.7.2
>            Reporter: Jason Lowe
>            Assignee: Junping Du
>            Priority: Critical
>             Fix For: 2.7.4
>
>         Attachments: HADOOP-13362-branch-2.7.patch
>
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message