[
https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036336#comment-15036336
]
Kuhu Shukla commented on YARN-4406:
-----------------------------------
Yes that is right, the issue is present on trunk. We could during
{{serviceInit}} populate this metric to the number of decommissioned nodes in
the inactive list, since we don't care about nodes that were decommissioned
before last restart AFAIK.
At present:
{code}
private void setDecomissionedNMsMetrics() {
Set<String> excludeList = hostsReader.getExcludedHosts();
ClusterMetrics.getMetrics().setDecommisionedNMs(excludeList.size());
}
{code}
To:
{code}
private void setDecomissionedNMsMetrics() {
int numDecommissioned = 0;
for(RMNode rmNode : rmContext.getInactiveRMNodes().values()) {
if (rmNode.getState() == NodeState.DECOMMISSIONED) {
numDecommissioned++;
}
}
ClusterMetrics.getMetrics().setDecommisionedNMs(numDecommissioned);
}
{code}
> RM Web UI continues to show decommissioned nodes even after RM restart
> ----------------------------------------------------------------------
>
> Key: YARN-4406
> URL: https://issues.apache.org/jira/browse/YARN-4406
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Ray Chiang
> Priority: Minor
>
> If you start up a cluster, decommission a NodeManager, and restart the RM,
> the decommissioned node list will still show a positive number (1 in the case
> of 1 node) and if you click on the list, it will be empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
