[
https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533359#comment-14533359
]
Xuan Gong commented on YARN-2331:
---------------------------------
[~jlowe] Could you rebase the patch, please ?
Probably, we could set the default value for
yarn.nodemanager.recovery.supervised as true. Normally, when people add a node
as NM, they expect to use this node for a long time. So, restart is expected ?
> Distinguish shutdown during supervision vs. shutdown for rolling upgrade
> ------------------------------------------------------------------------
>
> Key: YARN-2331
> URL: https://issues.apache.org/jira/browse/YARN-2331
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Labels: BB2015-05-TBR
> Attachments: YARN-2331.patch, YARN-2331v2.patch
>
>
> When the NM is shutting down with restart support enabled there are scenarios
> we'd like to distinguish and behave accordingly:
> # The NM is running under supervision. In that case containers should be
> preserved so the automatic restart can recover them.
> # The NM is not running under supervision and a rolling upgrade is not being
> performed. In that case the shutdown should kill all containers since it is
> unlikely the NM will be restarted in a timely manner to recover them.
> # The NM is not running under supervision and a rolling upgrade is being
> performed. In that case the shutdown should not kill all containers since a
> restart is imminent due to the rolling upgrade and the containers will be
> recovered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
