[
https://issues.apache.org/jira/browse/WHIRR-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002749#comment-13002749
]
David Alves commented on WHIRR-214:
-----------------------------------
{quote}It's also important to clearly explain the behaviour to users, since
there may be data loss scenarios.{quote}
Important point. What we could do here is to change either
ClusterActionHandlerSupport or ClusterActionHandler to add new lifecycle stages
that would execute before the Destroy stage. The rationale is that destroying a
cluster is different than decommissioning nodes from a cluster. By making these
changes and throwing UnsupportedOperationException by default services would
mandatorily have to deal with them in order for decommissioning to work.
I also agree with having some service support from the beginning but this
should probably go on another issue, right?
> Add nodes to running clusters
> -----------------------------
>
> Key: WHIRR-214
> URL: https://issues.apache.org/jira/browse/WHIRR-214
> Project: Whirr
> Issue Type: New Feature
> Reporter: Elliott Clark
>
> I would like to be able to add a node to a running cluster.
> For example if I have created a hadoop, hbase, zookeeper cluster I would like
> to be able to add region servers to hbase, Zookeeper nodes to the quorum,
> and task nodes to hadoop.
> Something akin to the functionality of the hbase-ec2 script. Where if I
> launch a node on an already running cluster. It is configured to join the
> cluster.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
