[jira] [Commented] (YARN-9202) RM does not track nodes that are in the include list and never register

["Kuhu Shukla (JIRA)" <ji...@apache.org>]

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

Kuhu Shukla commented on YARN-9202:
-----------------------------------

On second thought :
{quote}
bq. can they just be reused and moved to the NEW or RUNNING state when the host registers?

in the next patch.
{quote}
This is trickier as the old node will be set with the nodId = unknownNodeID and updating that needs change to RMNodeImpl fields some of which are private and final. Also when I tried making this change there were several typecasts to RMNodeImpl which makes this less than ideal. I will explore the two other possibilities to see which one makes more sense.

> 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
>
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org