[
https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945437#comment-13945437
]
Bikas Saha commented on YARN-556:
---------------------------------
Please align with the design doc while prototyping. If the design needs changes
then please update the document. The sub-tasks need to follow the design doc so
that other folks can follow even if they are not writing the code.
Some pieces of this are already underway in trunk (eg. RM not killing the
containers on app attempt exit). The scheduler changes are the most complex
piece. But they can come in the end. Working on trunk allows breaks/bugs to be
caught quicker and forces us to be more methodical in our approach. A branch is
useful when its not clear what approach to take or when we know the code is
going to be broken across commits. So I would prefer we do this on trunk.
> 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
>
>
> 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)
