Using each and local consistencies here gives you some safety in the transient
steps but also suggests you have control over when you move traffic
Is all traffic going to the first DC while you add the second?
If so, set RF=3 and run repair before you move traffic
If you were using quorum inst
Hi both, thank you for your responses!
Yes Jeff, we expect strictly correct responses. Our starting / ending
topologies are near-identical (DC1: A/B/C, DC2: A/B/C), and reads are
performed at LOCAL_QUORUM, while writes are done at EACH_QUORUM or ALL.
Thanks,
Sam
On Thu, Nov 25, 2021 at 9:38 AM J
The risk is not negligible if you expect strictly correct responses
The only way to do this correctly is very, very labor intensive at the moment,
and it requires repair between rebuilds and incrementally adding replicas such
that you don’t violate consistency
If you give me the starting topol
Yes, you are correct that the source may not necessarily be fully
consistent. But this risk is negligible if your cluster is sized-correctly
and nodes are not dropping mutations.
If your nodes are dropping mutations because they're overloaded and cannot
keep up with writes, rebuild is probably the
