hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2001) Persist NMs info for RM restart
Date Tue, 06 May 2014 02:41:17 GMT

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

Ming Ma commented on YARN-2001:
-------------------------------

1. In the HA set up, could we make standby RM hot by having NMs send heartbeat to all RMs?
 NMs will ignore the heartbeat response's commands from standby RMs. In that way, the new
active will have most recent NMs state right after the failover.

2. Decommission handling. If decommission state can be reconstructed via include and exclude
files, maybe we can ask admins to update include and exclude files on all RM nodes during
decommission process.

> 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)

Mime
View raw message