Thanks for answers. It went quite well. Note what Aaron writes about sstable
names, as I did the job before his mail, and changed one name wrong :-) - and
that caused some troubles ( a lot of missing file errors )- i think that was to
blame for some counter cf being messed up. As it was not
Sounds about right, i've done similar things before.
Some notes…
* I would make sure repair has completed on the source cluster before making
changes. I just like to know data is distributed. I would also do it once all
the moves are done.
* Rather than flush, take a snap shot and copy from
Hi,
I know this have been a topic here before, but I need some input on
how to move data from one datacenter to another (and google just gives
me some old mails) - and at the same time moving production writing
the same way. To add the target cluster into the source cluster and
just replicate
to get it correct, meaning consistent, it seems you will need to do
a repair no matter what since the source cluster is taking writes
during this time and writing to commit log. so to avoid filename
issues just do the first copy and then repair. i am not sure if they
can have any filename.
to
