of this cluster size would
> take?
>
>
>
> Regards,
>
> Christian
>
>
>
> *Von: *Rahul Singh
> *Antworten an: *"user@cassandra.apache.org"
> *Datum: *Donnerstag, 14. Juni 2018 um 14:21
> *An: *"user@cassandra.apache.org" , "
> user@cassand
,
Christian
Von: Rahul Singh
Antworten an: "user@cassandra.apache.org"
Datum: Donnerstag, 14. Juni 2018 um 14:21
An: "user@cassandra.apache.org" ,
"user@cassandra.apache.org"
Betreff: Re: Options to replace hardware of the cluster
How much daa do you have and what is t
How much daa do you have and what is the timeline? If you can manage with a
maintenance window the snapshot / move and restore method may be the fastest.
Streaming data can take a long time to sync two DCs if there is a lot of data.
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Jun 1
For no downtime and no lost data, I would make a new DC in the same cluster,
and wait for the data / MVs to stream over. Otherwise, the best way is to
snapshot everything and bring up the nodes all at once.
On Jun 14, 2018, 4:11 AM -0400, Christian Lorenz
, wrote:
> Hi,
>
> we need to move our e
Both are good options, a new data center in same cluster will work faster as
you can stream multiple nodes.
Or you can add 8 nodes to existing data center and then decommission one node
at a time but this is lengthy process including cleanup after decommission.
One node at a time is equally good.
Hi,
we need to move our existing cassandra cluster to new hardware nodes. Currently
the cluster size is 8 members, they need to be moved to 8 new machines.
Cassandra version in use is 3.11.1. Unfortunately we use materialized views in
production. I know that they have been marked retroactively
