[
https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945480#comment-13945480
]
Karthik Kambatla commented on YARN-556:
---------------------------------------
bq. 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.
Yes, that is the idea. The prototype should be mostly ready by end of the week.
Will update the document with any minor changes we see are required, along with
a prototype.
bq. The scheduler changes are the most complex piece. But they can come in the
end.
Without the scheduler changes, I am concerned the remaining patches would only
break things. The alternative is to have a config to enable work-preserving
restart and guard all changes by that config - I am not yet fully convinced of
this approach, would we want to leave this config even after the feature is
complete?
> 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)
