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 Thu, 09 Jan 2014 03:36:55 GMT

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

Jian He commented on YARN-1490:
-------------------------------

bq. What about NMTokens? Imagine this. AM1 requests a container, gets allocation and NMToken,
crashes, AM2 starts, wants to stop the container, but it doesn't have any NMToken.
TODO, will add the NMTokens for the containers on registration, I can do that in YARN-1041

> 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
>
>
> 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
(v6.1.5#6160)

Mime
View raw message