[
https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145044#comment-14145044
]
Jason Lowe commented on YARN-2523:
----------------------------------
Thanks for the patch, Rohith!
It seems inconsistent that we call incrDecommissionedNMs but never call
decrDecommissionedNMs, and I think it can cause problems. For example, if we
only have the include list specified but not an exclude list, nodes that
attempt to join that are not in the include list will go into the
DECOMMISSIONED state and increment the corresponding metric, but if we later
refresh the nodes then I think we'll set the metric for decommissioned nodes to
zero (because the exclude list is still empty) but there could be a non-zero
number of decommissioned nodes.
> ResourceManager UI showing negative value for "Decommissioned Nodes" field
> --------------------------------------------------------------------------
>
> Key: YARN-2523
> URL: https://issues.apache.org/jira/browse/YARN-2523
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, webapp
> Affects Versions: 3.0.0
> Reporter: Nishan Shetty
> Assignee: Rohith
> Attachments: YARN-2523.patch, YARN-2523.patch
>
>
> 1. Decommission one NodeManager by configuring ip in excludehost file
> 2. Remove ip from excludehost file
> 3. Execute -refreshNodes command and restart Decommissioned NodeManager
> Observe that in RM UI negative value for "Decommissioned Nodes" field is shown
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
