[
https://issues.apache.org/jira/browse/WHIRR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221501#comment-13221501
]
Russell Jurney commented on WHIRR-309:
--------------------------------------
It is WAY too hard to stop a Whirr cluster.
I just booted an elasticsearch cluster on EC2. Whirr cannot list clusters.
Stop cluster instructions were not printed when it started. I actually can't
figure it out. The destroy-cluster command is not working.
> Start/Stop Cluster Support
> --------------------------
>
> Key: WHIRR-309
> URL: https://issues.apache.org/jira/browse/WHIRR-309
> Project: Whirr
> Issue Type: New Feature
> Components: cli
> Environment: Amazon: Instances with an EBS root drive.
> Reporter: Travis Bolinger
> Priority: Minor
> Labels: features
>
> As per the discussion on IRC May 17, 2011.
> Add the ability for clusters to be stopped and started later while preserving
> data. AWS instances with an ebs root drive can be stopped and started again
> later while preserving data.
> Ideally, the Start/Stop ability will be available to other services besides
> Amazon.
> A note for amazon ebs instances (and possibly other services): when each node
> is started up again, it will receive a new IP address. Thus, the
> configuration files on each node may need to be changed to reflect the new IP
> addresses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
