Vinod Kumar Vavilapalli resolved YARN-128.
    Resolution: Fixed

Resolving this umbrella JIRA. RM recovery has largely been nearly 
complete/stable in YARN since this ticket was opened, what with its ultimate 
usage for rolling-upgrades (YARN-666).
 - As new issues come in, we can open new tickets.
- Will leave the open sub-tasks as they are.
- No fix-version as this was done across releases.

> [Umbrella] RM Restart Phase 1: State storage and non-work-preserving recovery
> -----------------------------------------------------------------------------
>                 Key: YARN-128
>                 URL: https://issues.apache.org/jira/browse/YARN-128
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: resourcemanager
>    Affects Versions: 2.0.0-alpha
>            Reporter: Arun C Murthy
>         Attachments: MR-4343.1.patch, RM-recovery-initial-thoughts.txt, 
> RMRestartPhase1.pdf, YARN-128.full-code-4.patch, YARN-128.full-code.3.patch, 
> YARN-128.full-code.5.patch, YARN-128.new-code-added-4.patch, 
> YARN-128.new-code-added.3.patch, YARN-128.old-code-removed.3.patch, 
> YARN-128.old-code-removed.4.patch, YARN-128.patch, 
> restart-12-11-zkstore.patch, restart-fs-store-11-17.patch, 
> restart-zk-store-11-17.patch
> This umbrella jira tracks the work needed to preserve critical state 
> information and reload them upon RM restart.

This message was sent by Atlassian JIRA

Reply via email to