Re: Splitting Cassandra Cluster between AWS availability zones

Hi, Before: 1 cluster with 2 DC. 3 nodes in each DCNow: 1 cluster with 1 DC. 6 nodes in this DC Is it right? If yes, depending on the RF - and assuming NetworkTopologyStrategy - I would do: - RF = 2  => 2 C* rack, one rack in each AZ - RF = 3  => 3 C* rack, one rack in each AZ In other words, I

Re: Splitting Cassandra Cluster between AWS availability zones

Hi Richard, It depends on the snitch and the replication strategy in use. Here's a link to a blogpost about how we deployed C* on 3AZ http://highscalability.com/blog/2016/8/1/how-to-setup-a-highly-available-multi-az-cassandra-cluster-o.html Best, Tommaso On Mar 7, 2017 18:05, "Ney, Richard"

Re: Splitting Cassandra Cluster between AWS availability zones

I'd recommend three availability zones. In this case if you loose one AZ you still have a quorum (assuming replication factor of 3) Andrey On Tue, Mar 7, 2017 at 9:05 AM, Ney, Richard wrote: > We’ve collapsed our 2 DC – 3 node Cassandra clusters into a single 6 node >

Splitting Cassandra Cluster between AWS availability zones

We’ve collapsed our 2 DC – 3 node Cassandra clusters into a single 6 node Cassandra cluster split between two AWS availability zones. Are there any behaviors we need to take into account to ensure the Cassandra cluster stability with this configuration? RICHARD NEY TECHNICAL DIRECTOR, RESEARCH