hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-556) RM Restart phase 2 - Work preserving restart
Date Sat, 10 May 2014 21:58:35 GMT

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

Karthik Kambatla commented on YARN-556:
---------------------------------------

For the scheduler-related work itself, the offline sync up thought it would be best to move
as much common code as possible to AbstractYarnScheduler. To unblock the restart work at the
earliest, we should do it in two phases - the first phase that only pulls out stuff that would
make it easier to handle the recovery, and a more comprehensive re-jig later.

> RM Restart phase 2 - Work preserving restart
> --------------------------------------------
>
>                 Key: YARN-556
>                 URL: https://issues.apache.org/jira/browse/YARN-556
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: resourcemanager
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: Work Preserving RM Restart.pdf, WorkPreservingRestartPrototype.001.patch
>
>
> YARN-128 covered storing the state needed for the RM to recover critical information.
This umbrella jira will track changes needed to recover the running state of the cluster so
that work can be preserved across RM restarts.



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

Mime
View raw message