hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits
Date Fri, 10 Jan 2014 01:13:51 GMT

    [ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867386#comment-13867386

Jian He commented on YARN-1490:

- New patch got rid of the local flag transferStateFromPreviousAttempt inside RMAppAttemptImpl
and SchedulerApplication, and notify the transferContainersFromPreviousAttempt through AppAddedSchedulerEvent
, and keepContainersAcrossAttempts through AppRemovedSchedulerEvent. 
- similar things for RMAppAttempt to notify RMApp for transferring the state through event.
- Fixed a bug in RMAppAttemptImpl.BaseFinalTransition. Missed to set the flag to false in
RMAppFailedAttemptEvent if this is the last attempt or unmanagedAM.

> RM should optionally not kill all containers when an ApplicationMaster exits
> ----------------------------------------------------------------------------
>                 Key: YARN-1490
>                 URL: https://issues.apache.org/jira/browse/YARN-1490
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Jian He
>         Attachments: YARN-1490.1.patch, YARN-1490.2.patch, YARN-1490.3.patch, YARN-1490.4.patch,
YARN-1490.5.patch, YARN-1490.6.patch, YARN-1490.7.patch, YARN-1490.8.patch
> This is needed to enable work-preserving AM restart. Some apps can chose to reconnect
with old running containers, some may not want to. This should be an option.

This message was sent by Atlassian JIRA

View raw message