> Now that I'm past the problems of IP addresses changing ... I am onto the
> idea of storage.  Initially I had though that for each cassandra instance, I
> should have an EBS volume to store all the cassandra data / information.
> Now I'm starting to wonder if this is duplication and not necessary.  If an
> instance dies, I loose anything that's not attached to EBS.  However, if the
> cassandra cluster is healthy ... this shouldn't be an issue ... Is this a
> correct assumption?

Correct.  Why not use EBS backed instances?  The ability to reboot comes in
handy.  I have a cluster of 6 nodes, each with an EBS drive of data (EBS
drives can scale, if you need them to - not advised).  Bootstrapping has
always worked better for me than doing any sort of data snapshotting,
allowing nodes to come in and out with proper token management.  You can
attach S3 buckets as drives as well...

On Wed, Mar 9, 2011 at 9:48 AM, Sasha Dolgy <sdo...@gmail.com> wrote:

> Hi Will,
> http://wiki.apache.org/cassandra/Operations#Backing_up_data
> <http://wiki.apache.org/cassandra/Operations#Backing_up_data>If the
> snapshot is written to the ephemeral storage ... there isn't a cost. (i need
> to confirm that)
> You can then move this to an S3 bucket with RDS if you want or full
> 99.999999999% redundancy and have it available to developers
> This is what I had in my head....
> -sd
> On Wed, Mar 9, 2011 at 5:39 PM, William Oberman 
> <ober...@civicscience.com>wrote:
>> I thought nodetool snapshot writes the snapshot locally, requiring 2x of
>> expensive storage allocation 24x7 (vs. cheap storage allocation of a ebs
>> snapshot).  By that I mean EBS allocation is GB allocated per month costs at
>> one rate, and EBS snapshots are delta compressed copies to S3.
>> Can you point the snapshot to an external filesystem?
>> will

Frank LoVecchio
isidorey.com | facebook.com/franklovecchio | franklovecchio.com

Reply via email to