hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1362) Distinguish between nodemanager shutdown for decommission vs shutdown for restart
Date Tue, 13 May 2014 13:35:15 GMT

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

Junping Du commented on YARN-1362:
----------------------------------

Thanks for the patch, [~jlowe]! I just start to work on rolling upgrade so need to understand
the preserving work in NM restart.
One question here: do we expect all shutdown ops on NM will hint it will get restart soon?
If not, the work will be preserved as isDecommssioned is set to false by default. Is that
the behavior we expect? 

> 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
>            Assignee: 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)

Mime
View raw message