: ebs or ephemeral
just catching the tail end of this discussion. aaron, in your previous
email, you said "And an explanation of why we normally avoid ephemeral. "
shouldn't this be, avoiding EBS? EBS was a nightmare for us in terms
of performance.
On Mon, Oct 10, 2011 at 9:23 A
yes, should have been
And an explanation of why we normally avoid *EBS*.
My bad.
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 10/10/2011, at 9:03 PM, Sasha Dolgy wrote:
> just catching the tail end of this discussion. aaron, in yo
just catching the tail end of this discussion. aaron, in your previous
email, you said "And an explanation of why we normally avoid ephemeral. "
shouldn't this be, avoiding EBS? EBS was a nightmare for us in terms
of performance.
On Mon, Oct 10, 2011 at 9:23 AM, aaron morton wrote:
> 6 nod
6 nodes and RF3 will mean you can handle between 1 and 2 failed nodes.
see http://thelastpickle.com/2011/06/13/Down-For-Me/
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 7/10/2011, at 9:37 PM, Madalina Matei wrote:
> Hi Aaron,
Hi Aaron,
For a 6 nodes cluster, what RF can we use in order to support 2 failed
nodes?
>From the article that you sent i understood "avoid EMS" and use ephemeral.
am i missing anything?
Thank you so much for your help,
Madaina
On Fri, Oct 7, 2011 at 9:15 AM, aaron morton wrote:
> Data Stax have
Data Stax have pre build AMI's here
http://www.datastax.com/dev/blog/setting-up-a-cassandra-cluster-with-the-datastax-ami
And an explanation of why we normally avoid ephemeral.
Also, I would go with 6 nodes. You will then be able to handle up to 2 failed
nodes.
Hope that helps.
-
Obviously ephemeral. It has higher IO availability, will not affect your
Ethernet IO performance, and it is free (included in instance price)
and the redundancy is provided by cassandra itself.
從我的 BlackBerry® 無線裝置
-Original Message-
From: Madalina Matei
Date: Fri, 7 Oct 2011 09:02:06
