You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/04/29 21:39:16 UTC

[jira] [Updated] (YARN-1362) Distinguish between nodemanager shutdown for decommission vs shutdown for restart

     [ https://issues.apache.org/jira/browse/YARN-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated YARN-1362:
-----------------------------

    Attachment: YARN-1362.patch

Small patch that enhances the NM context that provides get/set for a decomm flag.  This allows code to query whether the NM has been told to decommission and act accordingly during shutdown.

> Distinguish between nodemanager shutdown for decommission vs shutdown for restart
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-1362
>                 URL: https://issues.apache.org/jira/browse/YARN-1362
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>         Attachments: YARN-1362.patch
>
>
> When a nodemanager shuts down it needs to determine if it is likely to be restarted.  If a restart is likely then it needs to preserve container directories, logs, distributed cache entries, etc.  If it is being shutdown more permanently (e.g.: like a decommission) then the nodemanager should cleanup directories and logs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)