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

Hudson commented on YARN-7602:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13443 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13443/])
YARN-7602. NM should reference the singleton JvmMetrics instance. (haibochen: 
rev 2f6c038be6c23522ea64fc4e415910fb72493eb2)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/metrics/TestNodeManagerMetrics.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/metrics/NodeManagerMetrics.java
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/metrics2/source/TestJvmMetrics.java


> NM should reference the singleton JvmMetrics instance
> -----------------------------------------------------
>
>                 Key: YARN-7602
>                 URL: https://issues.apache.org/jira/browse/YARN-7602
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 3.0.0-beta1
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>             Fix For: 3.1.0, 3.0.1
>
>         Attachments: YARN-7602.00.patch, YARN-7602.01.patch, 
> YARN-7602.02.patch, YARN-7602.03.patch, YARN-7602.04.patch
>
>
> NM does not reference the singleton JvmMetrics instance in its 
> NodeManagerMetrics. This will easily cause NM to crash if any of the node 
> manager components tries to register JvmMetrics. An example of this is 
> TimelineCollectorManager that hosts a HBaseClient that registers JvmMetrics 
> again. See HBASE-19409 for details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to