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

Eric Payne commented on YARN-9202:
----------------------------------

[~kshukla], thank you for your detailed work in this patch.

I am generally fine with the patch, but there is one issue.

The current patch does not update the "Shutdown Nodes" list if a new node is 
added to the include list and refreshed.
For e.g.:
   # New node is installed named "host1.a.b.com" No Node Manager is running.
   # "host1.a.b.com" is added to tine include list.
   # run {{yarn rmadmin -refreshNodes

I would have expected "host1.a.b.com" to appear in the "Shutdown Nodes" list.

I spoke to [~kshukla] offline and she will determine if this is a 
straightforward thing to fix.

> RM does not track nodes that are in the include list and never register
> -----------------------------------------------------------------------
>
>                 Key: YARN-9202
>                 URL: https://issues.apache.org/jira/browse/YARN-9202
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.9.2, 3.0.3, 2.8.5
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>            Priority: Major
>         Attachments: YARN-9202.001.patch, YARN-9202.002.patch
>
>
> The RM state machine decides to put new or running nodes in inactive state 
> only past the point of either registration or being in the exclude list. This 
> does not cover the case where a node is the in the include list but never 
> registers and since all state changes are based on these NodeState 
> transitions, having NEW nodes be listed as inactive first may help. This 
> would change the semantics of how inactiveNodes are looked at today. Another 
> state addition might help this case too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to