You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2014/04/30 08:22:15 UTC

[jira] [Commented] (YARN-2001) Persist NMs info for RM restart

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

Jian He commented on YARN-2001:
-------------------------------

Persisting all the Nodes info definitely brings more overhead in a large cluster. It's a question of whether persisting all the nodes or simply introducing some kind of 'safe period', only after then AM requests are accepted and the NMs registered after that period are treated as new NM. 

> Persist NMs info for RM restart
> -------------------------------
>
>                 Key: YARN-2001
>                 URL: https://issues.apache.org/jira/browse/YARN-2001
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>
> RM should not accept allocate requests from AMs until all the NMs have registered with RM. For that, RM needs to remember the previous NMs and wait for all the NMs to register.
> This is also useful for remembering decommissioned nodes across restarts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)