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

Jason Lowe commented on YARN-4311:
----------------------------------

Sorry, I couldn't find a reference to {{isUntracked}} in trunk nor in 
YARN-3223.  So not sure if I understand exactly what is being asked.

To be consistent with HDFS the node should be gracefully decommissioned if it 
it appears in the include and exclude list simultaneously, otherwise once it's 
removed from the include list it's a hard decommission.

We could implement a "grace period" where nodes that were removed from the 
cluster are still "tracked" in the UI for a while before being removed.  That 
may help with some of the potentially confusing cases where a node is 
accidentally booted from the cluster.

> Removing nodes from include and exclude lists will not remove them from 
> decommissioned nodes list
> -------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4311
>                 URL: https://issues.apache.org/jira/browse/YARN-4311
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>         Attachments: YARN-4311-v1.patch
>
>
> In order to fully forget about a node, removing the node from include and 
> exclude list is not sufficient. The RM lists it under Decomm-ed nodes. The 
> tricky part that [~jlowe] pointed out was the case when include lists are not 
> used, in that case we don't want the nodes to fall off if they are not active.



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

Reply via email to