hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.
Date Thu, 29 Jan 2015 11:01:35 GMT

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

Devaraj K commented on YARN-41:
-------------------------------

Thanks [~djp] for your quick look.

bq. Given we already have decommission event, so this is for other cases, e.g. shutdown NM
daemon through CLI. Isn't it?
correct, It is to avoid the RM waiting for NM expiry interval to move down-NM from active
to lost when NM shutdown is graceful.

bq. If so, we should consider the case that NM work preserving is enabled (for rolling upgrade),
and these nodes shouldn't be unregister to RM.
I realize now that RM kills all the running containers when the NM changes state from active
to decommissioned. Thanks for pointing this, will consider this case.

> The RM should handle the graceful shutdown of the NM.
> -----------------------------------------------------
>
>                 Key: YARN-41
>                 URL: https://issues.apache.org/jira/browse/YARN-41
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, resourcemanager
>            Reporter: Ravi Teja Ch N V
>            Assignee: Devaraj K
>         Attachments: MAPREDUCE-3494.1.patch, MAPREDUCE-3494.2.patch, MAPREDUCE-3494.patch,
YARN-41-1.patch, YARN-41-2.patch, YARN-41-3.patch, YARN-41.patch
>
>
> Instead of waiting for the NM expiry, RM should remove and handle the NM, which is shutdown
gracefully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message