[
https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542045#comment-14542045
]
Junping Du commented on YARN-41:
--------------------------------
Thanks [~jlowe] for sharing this prospective. I think YARN-3212 is facing the
same situation as your last comment there.
However, in this case, we may make things simpler if we don't care if running
applications on work preserving enabled nodes. We just simply don't do
unRegister NM from RM when work-preserving is enabled - this is not only
simpler for implementation, but also simpler for user to understand - or it
will make shutdown NM daemon's behavior sounds more randomly as sometimes it
get disappeared from RM while sometimes not - this sounds the behavior is not
controlled by configuration but controlled by randomly container allocation.
Thoughts?
> 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
> Labels: BB2015-05-TBR
> 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-4.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)
