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

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

Thanks [~devaraj.k]. Sorry for missing an important comment on current patch: 
>From many discussions in umbrella JIRA (YARN-914), most of us prefer not to 
>pass timeout value to YARN RM side but make it proper handled in RMAdmin side 
>which make things much simpler (please check discussion there for more 
>details). So the CLI with -g option could be a blocked CLI until all nodes get 
>decommissioned or timeout.
Psudo logic in this CLI should be something like: 
{code}
refreshNodeGracefully(); - mark node to decommissionning
while (!timeout && some nodes still in decommissioning) {
  checkStatusForDecommissioningNodes();
}
if (timeout) {
  refreshNode forcefully for reminding nodes
}
{code}
Thoughts?

> 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)

Reply via email to