[
https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-1489.
-------------------------------------------
Resolution: Fixed
Assignee: (was: Vinod Kumar Vavilapalli)
Resolved this very old feature as fixed. Keeping it unassigned given multiple
contributors. No fix-version given the tasks (perhaps?) spanned across releases.
> [Umbrella] Work-preserving ApplicationMaster restart
> ----------------------------------------------------
>
> Key: YARN-1489
> URL: https://issues.apache.org/jira/browse/YARN-1489
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Priority: Major
> Attachments: Work preserving AM restart.pdf
>
>
> Today if AMs go down,
> - RM kills all the containers of that ApplicationAttempt
> - New ApplicationAttempt doesn't know where the previous containers are
> running
> - Old running containers don't know where the new AM is running.
> We need to fix this to enable work-preserving AM restart. The later two
> potentially can be done at the app level, but it is good to have a common
> solution for all apps where-ever possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
