[
https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995511#comment-13995511
]
Tsuyoshi OZAWA commented on YARN-556:
-------------------------------------
If we can break the compatibility about the container id, I think Anubhav's
approach has no problem.
If we cannot do this as [~jianhe] mentioned on YARN-2001, I think epoch idea
[described
here|https://issues.apache.org/jira/browse/YARN-2001?focusedCommentId=13995213&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13995213]
might be used.
> 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)
