restart cassandra after instances stop/start
Hi, I followed the instructions here http://nubetech.co/setting-up-cassandra-clusters-in-the-cloud-with-whirr to set up an ec2 cluster on AWS. Everything works great until I stop my instances (to save money) and restart them because the instances get new IPs. What changes do I need to make in order to get my cassandra cluster up and running again? Thanks. Regards, -k
[ANNOUNCE] Apache Whirr 0.5.0-incubating released
The Apache Whirr team is pleased to announce the release of Whirr 0.5.0-incubating from the Apache Incubator. This is the fifth incubating release of Apache Whirr, a set of libraries for running cloud services such as Apache Hadoop, HBase, ZooKeeper, and Cassandra. The release is available here: http://www.apache.org/dyn/closer.cgi/incubator/whirr/ The full change log is available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316248styleName=HtmlprojectId=1230 We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://incubator.apache.org/whirr/ The Apache Whirr Team
Re: restart cassandra after instances stop/start
I see.. What if I only need to resume the cluster and don't worry about any data? Each time I use whirr to set up a new clusters, new EBS volumes are also created and I got charged for the volumes at full month rate even though I only use them for a few hours.Thanks. -k On Sun, Jun 5, 2011 at 5:43 PM, Andrei Savu savu.and...@gmail.com wrote: Hi, There is no easy way to suspend a cluster started with Whirr without loosing all the data stored on the nodes. You need a custom tool to export and save data on shutdown (maybe to S3) and load it back when you start the cluster again. We are tracking progress on this issue here: https://issues.apache.org/jira/browse/WHIRR-309 Cheers, -- Andrei Savu / andreisavu.ro On Mon, Jun 6, 2011 at 12:34 AM, Khanh Nguyen nguyen.h.kh...@gmail.com wrote: Hi, I followed the instructions here http://nubetech.co/setting-up-cassandra-clusters-in-the-cloud-with-whirr to set up an ec2 cluster on AWS. Everything works great until I stop my instances (to save money) and restart them because the instances get new IPs. What changes do I need to make in order to get my cassandra cluster up and running again? Thanks. Regards, -k
