[
https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036616#comment-15036616
]
Kuhu Shukla commented on YARN-4406:
-----------------------------------
I agree. I was thinking about that too. During {{registerwithRM()}} we throw a
YarnException while on the ResourceTrackerService side we just send NodeAction
as SHUTDOWN. We could in fact update InactiveRMNode list with this node, so
that it is consistent. Let me know what you think. I will put up a patch soon.
> 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
> Assignee: Kuhu Shukla
> 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)
