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 would align C* rack and AZ.Note that AWS charges for inter AZ
traffic a.k.a Regional Data Transfer.
Best,
Romain
Le Mardi 7 mars 2017 18h36, tommaso barbugli <tbarbu...@gmail.com> a écrit :
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" <richard....@aspect.com> wrote:
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 NEYTECHNICAL DIRECTOR, RESEARCH &
DEVELOPMENTUNITED statesrichard....@aspect.comaspect.com This email (including
any attachments) is proprietary to Aspect Software, Inc. and may contain
information that is confidential. If you have received this message in error,
please do not read, copy or forward this message. Please notify the sender
immediately, delete it from your system and destroy any copies. You may not
further disclose or distribute this email or its attachments.
