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

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

[~templedf]

Also, YARN-4386 would still be needed since currently we are looking for 
DECOMMISSIONED nodes in list returned by getRMNodes() which does not contain 
nodes in that state. Such nodes are part of getInactiveRMNodes list. So the 
change would still be needed even if we decide to add transition from DECOMM to 
RECOMM or not. 

I also had a question about the DECOMM to RECOMM transition and please pardon 
any naivety. If we transition a node which is not running NM process any more 
since its was DECOMM-ed and would then be SHUTDOWN, how does a RECOMM event 
help this node, unless we decide to start the NM process? Am I missing 
something here? Appreciate any comments.

> 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
>         Attachments: YARN-4413.001.patch
>
>
> 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