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

Kuhu Shukla commented on YARN-4413:
-----------------------------------

Thanks for reporting this [~templedf]. Was a node refresh done after the file 
change ? If yes then I think,  since this metric is updated during 
AddNodeTransition (which updates rejoined metrics) , there is no transition 
that takes care of this until the node tries to register/heartbeat (as it is 
absent from all RMNodeImpl lists). One way could be to do this check in 
{{refreshNodes}}. 

> Nodes in the includes list should not be listed as decommissioned in the UI
> ---------------------------------------------------------------------------
>
>                 Key: YARN-4413
>                 URL: https://issues.apache.org/jira/browse/YARN-4413
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> If I decommission a node and then move it from the excludes list back to the 
> includes list, but I don't restart the node, the node will still be listed by 
> the web UI as decomissioned until either the NM or RM is restarted.  Ideally, 
> removing the node from the excludes list and putting it back into the 
> includes list should cause the node to be reported as shutdown instead.
> CC [~kshukla]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to