[
https://issues.apache.org/jira/browse/YARN-9202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744369#comment-16744369
]
Kuhu Shukla commented on YARN-9202:
-----------------------------------
Here is an initial patch that tackles this problem by listing new nodes as
SHUTDOWN first. This means that now nodes can be shutdown and be brought back
up making it a non terminal state in say one life cycle of the RM. Any ideas,
concerns around this change which can cause semantics to break would be good to
point out here. I will wait for p\Precommit before formal review comment
request but any ideas on this patch would be awesome!
> 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: [email protected]
For additional commands, e-mail: [email protected]
