ly 2
> nodes in each of the 3 racks?
>
>
>
> - Justin Sanciangco
>
>
>
>
>
> *From: *Alexander Dejanovski
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Tuesday, March 12, 2019 at 10:56 AM
> *To: *user
> *Subject: *Re: Changing existin
2 nodes in each of
the 3 racks?
- Justin Sanciangco
From: Alexander Dejanovski
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, March 12, 2019 at 10:56 AM
To: user
Subject: Re: Changing existing Cassandra cluster from single rack configuration
to multi racks configuration
t;
>
> *From: *Laxmikant Upadhyay
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Monday, March 11, 2019 at 10:52 PM
> *To: *"user@cassandra.apache.org"
> *Subject: *Re: Changing existing Cassandra cluster from single rack
> configuration to multi racks configurati
On Tue, Mar 12, 2019 at 5:28 PM Justin Sanciangco
wrote:
> I would recommend that you do not go into a 3 rack single dc
> implementation with only 6 nodes. If a node goes down in this situation,
> the node that is paired with the node that is downed will have to service
> all of the load instead
te: Monday, March 11, 2019 at 10:52 PM
To: "user@cassandra.apache.org"
Subject: Re: Changing existing Cassandra cluster from single rack configuration
to multi racks configuration
Hi Alex,
Regarding your below point the admin need to take care of temporary uneven
distribution of data uti
Hi Alex,
Regarding your below point the admin need to take care of temporary uneven
distribution of data util the entire process is done:
"If you can't, then I guess you can for each node (one at a time),
decommission it, wipe it clean and re-bootstrap it after setting the
appropriate rack."
I
Hi Manish,
the best way, if you have the opportunity to easily add new
hardware/instances, is to create a new DC with racks and switch traffic to
the new DC when it's ready (then remove the old one). My co-worker Alain
just wrote a very handy blog post on that technique :
We have a 6 node Cassandra cluster in which all the nodes are in same rack
in a dc. We want to take advantage of "multi rack" cluster (example:
parallel upgrade on all the nodes in same rack without downtime). I would
like to know what is the recommended process to change an existing cluster
with
