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
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
Please let me know the best practices to combine 2 different cluster's into
one without having any downtime.
Thanks & Regards,
Nanda Kishore
This is a multi-dc cluster with public IPs for the nodes and also addressed
with private IPs as well in AWS. The apps connect via java-driver to a
public IP.
When we built the 2.1.X cluster with ec2multiregionsnitch, the system.peers
table had public ips for the nodes in the rpc_address column.
Kenneth,
Thank you for the reply, and sorry for my late response. I did not notice
this had a reply until just now!
To answer your questions:
In this statement from your email:
>
> SELECT * FROM m_ps_project_policy_device4 where project_id=1337 and
> policy_id=7331 and device_id='1234567890'
