[
https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509663#comment-13509663
]
Strahinja Lazetic commented on YARN-128:
----------------------------------------
Bikas, I have one question; Since we reboot NMs and terminate all the running
containers and AMs upon the RM restart, why do we need to keep track of the
previous Applications' attempts? Couldn't we just start "from scratch" instead
of generating the next attempt id based on the last running one?
> Resurrect RM Restart
> ---------------------
>
> Key: YARN-128
> URL: https://issues.apache.org/jira/browse/YARN-128
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.0-alpha
> Reporter: Arun C Murthy
> Assignee: Bikas Saha
> Attachments: MR-4343.1.patch, restart-12-11-zkstore.patch,
> restart-fs-store-11-17.patch, restart-zk-store-11-17.patch,
> RM-recovery-initial-thoughts.txt, RMRestartPhase1.pdf,
> YARN-128.full-code.3.patch, YARN-128.full-code-4.patch,
> YARN-128.full-code.5.patch, YARN-128.new-code-added.3.patch,
> YARN-128.new-code-added-4.patch, YARN-128.old-code-removed.3.patch,
> YARN-128.old-code-removed.4.patch, YARN-128.patch
>
>
> We should resurrect 'RM Restart' which we disabled sometime during the RM
> refactor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
