[
https://issues.apache.org/jira/browse/YARN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-2331:
-----------------------------
Attachment: YARN-2331.patch
In the interest of getting something done for this in time for 2.6, here's a
patch that adds a conf to tell the NM whether or not it's supervised. If
supervised then it is expected to be quickly restarted on shutdown and will not
kill containers. If unsupervised then it will kill containers on shutdown
since it does not expect to be restarted in a timely manner.
> 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
> Attachments: YARN-2331.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)
