I would recommend creating a second Cassandra Datacenter for the cluster, rather than single nodes in the same DC, this is likely to cause latency issues, due to quorum queries being across datacenters.
We did this several times, moving from Rackspace to GCP, this is all documented in 3 blog posts starting here: https://www.redshots.com/moving-cassandra-clusters-without-downtime-part-1/ If you have any further questions let me know. Thanks Paul > On 11 Apr 2022, at 10:52, Germain MAURICE <germain.maur...@oscaro.com> wrote: > > Hello, > In my company we are working on migrating our cassandra cluster from a > provider to another one, we plan to migrate the data adding a node and > decommissioning an old one. > We would like to throttle the bandwith used between the both providers to > preserve the capacity of the link. > We would to like to confirm if the process of migration and throughput > throttling we plan is the right one. > The plan is the following : > installing a new node on gcp > setting streamthroughput on each on-premise node (3 nodes) that will ensure > we don’t use more than 3 * streamthrougput of bandwith of the link between > the both provider > launch ˋnodetool decommission` on an on-premise node > wait for the end of the decommission > Is that right ? > Thank you for your answer.
