Either: double-write at the driver level from one of the apps and perform an initial and a subsequent sstable loads (or whatever ETL method you want to use) to merge the data with good assurances.
use a trigger to replicate the writes, with some sstable loads / ETL. use change data capture with some sstable loads/ETL On Mon, Mar 25, 2019 at 5:48 PM Nick Hatfield <nick.hatfi...@metricly.com> wrote: > Maybe others will have a different or better solution but, in my > experience to accomplish HA we simply y write from our application to the > new cluster. You then export the data from the old cluster using cql2json > or any method you choose, to the new cluster. That will cover all live(now) > data via y write, while supplying the old data from the copy you run. Once > complete, set up a single reader that reads data from the new cluster and > verify all is as expected! > > > Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. > *From: *Nandakishore Tokala > *Sent: *Monday, March 25, 2019 18:39 > *To: *user@cassandra.apache.org > *Reply To: *user@cassandra.apache.org > *Subject: *Merging two cluster's in to one without any downtime > > Please let me know the best practices to combine 2 different cluster's > into one without having any downtime. > > Thanks & Regards, > Nanda Kishore >
