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
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.
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
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
Kurt,
Hint file matches UUID matches with another node in the cluster:
-rw-r--r--. 1 root root 6848246 May 13 23:37
1b694180-210a-4b75-8f2a-748f4a5b6a3d-1526254645089-1.hints
/opt/cassandra/bin/nodetool status |grep 1b694180
UN x.x.x. 23.77 GiB 256 ?
1b694180-210a-4b75-8f2a-748f4a
Hey Chris,
Sorry to bother you. Did you get a chance to look at the gclog file I sent
last night.
On Wed, Jun 13, 2018, 8:44 PM rajpal reddy wrote:
> Chris,
>
> sorry attached wrong log file. attaching gc collection seconds and cpu.
> there were going high at the same time and also attached the
