replicator Think about bi-directional sync

Think about bi-directional sync

Open bobvawter opened this issue 3 years ago • 3 comments

Discussion issue for thinking about how two clusters could be kept in eventual-sync:

Source/destination cluster tracking column to avoid looping cdc-sink'ed mutations
MVCC timestamp comparison to drop too-old events from source cluster
Conflict resolution detection / logic?

Dec 01 '21 22:12 bobvawter

Playing with compare-and-set and deadlines in #86.

Jan 27 '22 21:01 bobvawter

@bobvawter , is there anything else needed for this?

Sep 15 '23 19:09 BramGruneir

Yes, three-way merge via the userscript.

Sep 17 '23 16:09 bobvawter

Is this addressed by LDR now? Or is it bi-directional sync between any combination of C2X?

Oct 05 '24 03:10 ryanluu12345