So, sstableloader streams a portion of data stored in
/var/lib/cassandra/data/keyspace/table catalog
If we have 3 nodes and RF=3, then only 1/3 of data would be streamed to
other cluster.
Problem is solved.
2015-04-01 12:05 GMT+02:00 Alain RODRIGUEZ arodr...@gmail.com:
From Michael Laing -
From Michael Laing - posted on the wrong thread :
We use Alain's solution as well to make major operational revisions.
We have a red team and a blue team in each AWS region, so we just add
and drop datacenters to get where we want to be.
Pretty simple.
2015-03-31 15:50 GMT+02:00 Alain
Hi, I have a simple question and can't find related info in docs.
I have cluster1 with 3 nodes and cluster2 with 5 nodes. I want to transfer
whole keyspace named 'mykeyspace' data from cluster1 to cluster2 using
sstableloader. I understand that it's not the best solution, I need it for
testing
Hi,
Despite of I understand that it's not the best solution, I need it for
testing purposes, I have to ask you if you considered doing an Alter
keyspace, change RF 1 for mykeyspace on cluster2 and nodetool rebuild
to add a new DC (your cluster2) ?
In the case you go your way (sstableloader)
IMHO, the most straight forward solution is to add cluster2 as a new DC for
mykeyspace and then drop the old DC.
That's how we migrated to VPC (AWS) and we love this approach since you
don't have to mess with your existing cluster, plus sync is made
automatically and you can then drop your old DC
I have to ask you if you considered doing an Alter keyspace, change RF
The idea is dead simple:
get data from cluster1,
put it to cluster2
vipe cluster1
I understand drawbacks of streaming sstableloader approach, I need right
now something easy. Later we consider switch to Priam since it does
