Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-13 Thread Dave Martorana
To: Jeremiah Peschka jeremiah.pesc...@gmail.com Cc: riak-users riak-users@lists.basho.com Subject: Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?) Message-ID: cacusovelpu8yfcivykexm9ztkhq-kdnowk1afvpflcsip2h...@mail.gmail.com Content-Type: text/plain; charset=iso-8859

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-13 Thread Brady Wetherington
jeremiah.pesc...@gmail.com Cc: riak-users riak-users@lists.basho.com Subject: Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?) Message-ID: cacusovelpu8yfcivykexm9ztkhq-kdnowk1afvpflcsip2h...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 +1 to what

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-13 Thread John Eikenberry
Brady Wetherington wrote: First off - I know 5 instances is the magic number of instances to have. If I understand the thinking here, it's that at the default redundancy level ('n'?) of 3, it is most likely to start getting me some scaling (e.g., performance just that of a single node), and

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-13 Thread Matthew Dawson
On August 13, 2013 10:20:48 PM Brady Wetherington wrote: One thing that I *think* I've figured out is that the number of how many replicas can you lose and stay up is actually n-w for writes, and n-r for reads - So with n=3 and r=2 and w=2, the loss of two replicas due to AZ failure means

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-12 Thread Dave Martorana
Jared - thanks for the links. I'm in the same boat with Brady with weighing deployment options in AWS. Jeremiah - isn't EBS the only option once your data starts reaching into the hundreds-of-gigs? Dave On Sun, Aug 11, 2013 at 8:57 PM, Jared Morrow ja...@basho.com wrote: +1 to what Jeremiah

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-12 Thread Jeremiah Peschka
Nope, depending on how much you want to spend, you can cram up to 42TB into a single AWS instance. Reasonably priced instances can hold 1690GB of data on a single instance. You can see an easy to sort map over here: http://www.ec2instances.info/ I would take Amazon's own recommendations with a

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-12 Thread Hector Castro
On Mon, Aug 12, 2013 at 2:38 PM, Dave Martorana d...@flyclops.com wrote: Jared - thanks for the links. I'm in the same boat with Brady with weighing deployment options in AWS. Jeremiah - isn't EBS the only option once your data starts reaching into the hundreds-of-gigs? Several instances

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-12 Thread Brady Wetherington
To: Jeremiah Peschka jeremiah.pesc...@gmail.com Cc: riak-users riak-users@lists.basho.com Subject: Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?) Message-ID: cacusovelpu8yfcivykexm9ztkhq-kdnowk1afvpflcsip2h...@mail.gmail.com Content-Type: text/plain; charset=iso

Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-11 Thread Brady Wetherington
Hi all - I have some questions about how I want my Riak stuff to work - I've already asked these questions of some Basho people and gotten some answers, but thought I would toss it out into the wider world to see what you all have to say, too: First off - I know 5 instances is the magic number

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-11 Thread Jeremiah Peschka
I'd be wary of using EBS backed nodes for Riak - with only a single ethernet connection, it wil be very easy to saturate the max of 1000mbps available in a single AWS NIC (unless you're using cluster compute instances). I'd be more worried about temporarily losing contact with a node through

Re: Practical Riak cluster choices in AWS (number of nodes? AZ's?)

2013-08-11 Thread Jared Morrow
+1 to what Jeremiah said, putting a 4 or 5 node cluster in each US West and US East using MDC between them would be the optimum solution. I'm also not buying consistent latencies between AZ's, but I've also not tested it personally in a production environment. We have many riak-users members on