cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Franc Carter <franc.car...@sirca.org.au>
Subject Re: two-node cassandra cluster
Date Sun, 26 Aug 2012 21:57:11 GMT
On Fri, Aug 24, 2012 at 8:25 PM, Jason Axelson <jason@engagestage.com>wrote:

> Hi, I have an application that will be very dormant most of the time
> but will need high-bursting a few days out of the month. Since we are
> deploying on EC2 I would like to keep only one Cassandra server up
> most of the time and then on burst days I want to bring one more
> server up (with more RAM and CPU than the first) to help serve the
> load. What is the best way to do this? Should I take a different
> approach?
>
> Some notes about what I plan to do:
> * Bring the node up and repair it immediately
> * After the burst time is over decommission the powerful node
> * Use the always-on server as the seed node
> * My main question is how to get the nodes to share all the data since
> I want a replication factor of 2 (so both nodes have all the data) but
> that won't work while there is only one server. Should I bring up 2
> extra servers instead of just one?
>
> Thanks,
> Jason
>

Caveat: I haven't tried what I am about to suggest

Could you run the cluster on smaller instances for most of the time and
then when you need more performance increases the instance size to get more
CPU/Memory. If you use EBS with provisioned IOPs you should be able to make
the transition reasonably quickly.

cheers

-- 

*Franc Carter* | Systems architect | Sirca Ltd
 <marc.zianideferranti@sirca.org.au>

franc.carter@sirca.org.au | www.sirca.org.au

Tel: +61 2 9236 9118

Level 9, 80 Clarence St, Sydney NSW 2000

PO Box H58, Australia Square, Sydney NSW 1215

Mime
View raw message