Basically it's all variations of alter keyspace command, depends on your
actual starting point.
ALTER KEYSPACE mykespace WITH replication = { 'class' :
'NetworkTopologyStrategy', 'replication_factor': '3', '<exiting_dc>' : 3,
<new_dc> : 4};The best is to play a bit with multi DC setup with docker images and repeat it with a test dataset until you are confidence about the commands and their outcome. This example should work with Cassandra: https://www.scylladb.com/2018/03/28/mms-day7-multidatacenter-consistency/ On Sat, Jan 5, 2019 at 5:57 AM R1 J1 <[email protected]> wrote: > Dor Laor, > I like your approach. If I restrict the replication factor of a keyspace > to on premise data center and another to azure and attempt to split the > cluster? > Do you have some documentation I can refer to ? > > Regards > R1J1 > > On Fri, Jan 4, 2019 at 5:32 PM Dor Laor <[email protected]> wrote: > >> Not sure I understand correctly but if you have one cluster with 2 >> separate datacenters >> you can define keyspace A to be on premise with a single DC and keyspace >> B only on Azure. >> >> >> On Fri, Jan 4, 2019 at 2:23 PM R1 J1 <[email protected]> wrote: >> >>> We currently have 2 databases (A and B ) on a 6 node cluster. >>> 3 nodes are on premise and 3 in azure. I want database A to live on >>> onpremise cluster and I want Database B to stay in the Azure. I want to >>> then split the cluster into 2 clusters one onpremise (3 node ) having >>> Database A and other in Azure (3 node ) having Database B. >>> >>> How do we accomplish such a split ? >>> >>> >>> Regards >>> R1J1 >>> >>
