[
https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356331#comment-14356331
]
Devaraj K commented on YARN-3225:
---------------------------------
bq. not to pass timeout value to YARN RM side but make it proper handled in
RMAdmin side which make things much simpler
Here what would happen to the decommissioning node if the RMAdmin issued
refreshNodeGracefully() and gets terminated(exited) before issuing the
'refreshNode forcefully'? This can be done by doing Ctrl+C on the command
prompt. The Node will be in decommissioning state forever and becomes unusable
for new containers allocation.
> New parameter or CLI for decommissioning node gracefully in RMAdmin CLI
> -----------------------------------------------------------------------
>
> Key: YARN-3225
> URL: https://issues.apache.org/jira/browse/YARN-3225
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Junping Du
> Assignee: Devaraj K
> Attachments: YARN-3225.patch, YARN-914.patch
>
>
> New CLI (or existing CLI with parameters) should put each node on
> decommission list to decommissioning status and track timeout to terminate
> the nodes that haven't get finished.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
