[
https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360591#comment-14360591
]
Devaraj K commented on YARN-3225:
---------------------------------
I was describing in my previous comment about having two RMAdmin CLI's for
increasing the timeout value, one CLI runs with the timeout(say ‘x’) value and
continues waiting for timeout, during this time another CLI issues the command
with the higher timeout(>x). If we keep the CLI(x timeout) running it would
issue the forceful decommission with x timeout and new CLI timeout(>x) will not
reflect. If we have a constraint that we should issue graceful decommission
command from only one RMAdmin CLI then this issue will not be a problem.
> 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)
