[
https://issues.apache.org/jira/browse/YARN-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905785#comment-13905785
]
Hadoop QA commented on YARN-1071:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12629826/YARN-1071.2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3122//console
This message is automatically generated.
> ResourceManager's decommissioned and lost node count is 0 after restart
> -----------------------------------------------------------------------
>
> Key: YARN-1071
> URL: https://issues.apache.org/jira/browse/YARN-1071
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Srimanth Gunturi
> Assignee: Jian He
> Attachments: YARN-1071.1.patch, YARN-1071.2.patch
>
>
> I had 6 nodes in a cluster with 2 NMs stopped. Then I put a host into YARN's
> {{yarn.resourcemanager.nodes.exclude-path}}. After running {{yarn rmadmin
> -refreshNodes}}, RM's JMX correctly showed decommissioned node count:
> {noformat}
> "NumActiveNMs" : 3,
> "NumDecommissionedNMs" : 1,
> "NumLostNMs" : 2,
> "NumUnhealthyNMs" : 0,
> "NumRebootedNMs" : 0
> {noformat}
> After restarting RM, the counts were shown as below in JMX.
> {noformat}
> "NumActiveNMs" : 3,
> "NumDecommissionedNMs" : 0,
> "NumLostNMs" : 0,
> "NumUnhealthyNMs" : 0,
> "NumRebootedNMs" : 0
> {noformat}
> Notice that the lost and decommissioned NM counts are both 0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
