hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI
Date Fri, 13 Mar 2015 17:16:39 GMT

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

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

bq.  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.
Can we have this assumption in our first phase (target to catch up 2.8)? IMO, Decommissioning
nodes is very restrictive operation that we don't expect multiple could happen at the same
time on a cluster. We can improve later if we think this is not good enough. 

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

Mime
View raw message