[
https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895761#comment-13895761
]
Bikas Saha commented on YARN-1490:
----------------------------------
The option to kill container on AM exit should come from
AM.registerApplicationMaster and not from
client.submitApplication(AppSubmissionContext). The AM is the one who knows
whether it can recover running containers after restart. So its the AM who
should tell the RM whether to kill containers upon AM restart. Consider the
case when a generic client is submitted a bunch of a class of apps or the same
app client is submitting apps with different versions of the AM code. Some
apps/versions may support this feature and some may not. Its the app that
should tell the RM what to do based on what the app is capable of.
> 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
> Fix For: 2.4.0
>
> Attachments: YARN-1490.1.patch, YARN-1490.10.patch,
> YARN-1490.11.patch, YARN-1490.11.patch, YARN-1490.12.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, YARN-1490.9.patch,
> org.apache.oozie.service.TestRecoveryService_thread-dump.txt
>
>
> 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)
