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

Junping Du commented on YARN-3225:
----------------------------------

Thanks [~devaraj.k] for replying.
bq. If the user wants to achieve this, they can give some larger timeout value 
and wait for all nodes to get decommissioned gracefully(without forceful). Do 
we really need to provide special handling for this case?
It would be great if we can support this case because users doesn't have to 
think out a large number for an important job and doesn't known when to end. 
Given this is a trivial effort comparing what you already achieved, we'd better 
do here instead of filing a separated JIRA. What do you think?

bq. I feel "Decommission nodes in normal way" would be ok, no need to mention 
the 'old' term. What is your opinion on this?
Yes. That sounds good. My previous point is not to mention "decommissioning" 
for normal/previous decommission process to get rid of any confusing.

> 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-1.patch, YARN-3225-2.patch, YARN-3225-3.patch, 
> 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)

Reply via email to