[
https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162794#comment-15162794
]
Junping Du commented on YARN-1489:
----------------------------------
bq. That and the "Old running containers don't know where the new AM is
running." issue is big enough that we shouldn't close this umbrella as done.
I don't think we have an open JIRA under this umbrella to track this issue. Is
this a specific issue for MR (like we discussed on MAPREDUCE-6608) or a generic
issue for other frameworks (Spark, etc.) too? YARN-4602 get filed to track this
issue as a generic problem for messages pass between containers.
> [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
> Assignee: Vinod Kumar Vavilapalli
> 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
(v6.3.4#6332)
