[
https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542192#comment-14542192
]
Devaraj K commented on YARN-41:
-------------------------------
Thanks Vinod, Junping and Jason for the discussion here.
bq. So we should check two configurations together, only skip unregister in
case both configuration are true. Isn't it?
If we unregister when node preserving is enabled and NM is not under
supervision, we would be falling to the YARN-3535 issue again. For skipping
unregister, checking whether node preserving is enabled or not wouldn't
sufficient irrespective of nm is under supervision or not?
> 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)
