[jira] [Commented] (YARN-558) Add ability to completely remove nodemanager from resourcemanager.

["Christian Smith (JIRA)" <ji...@apache.org>]

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

Christian Smith commented on YARN-558:
--------------------------------------

+1 For this as well.  

This is essential for any public (or private) cloud scenario where one wants elastic clusters.

> Add ability to completely remove nodemanager from resourcemanager.
> ------------------------------------------------------------------
>
>                 Key: YARN-558
>                 URL: https://issues.apache.org/jira/browse/YARN-558
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Garth Goodson
>            Priority: Minor
>              Labels: feature
>
> I would like to add the ability to completely remove a nodemanager from the resourcemanager's state.
> I run a cloud service where I want to dynamically bring up nodes to act as nodemanagers and then bring them down again when not needed.  These nodes have dynamically assigned IPs, thus the alternative of decommissioning them via an excludes file leads to a large (unbounded) list of decommissioned nodes that may never be commissioned again. I would like the ability to move a node from a decommissioned state to completely removing it from the resource manager.
> I have thought of two ways of implementing this.
> 1) Add an optional timeout between the decommission state -> being removed from the nodemanager.
> 2) Add an explicit RPC to remove a node that is decommissioned.
> Any additional thoughts/discussion are welcome.



--
This message was sent by Atlassian JIRA
(v6.2#6252)