multi-leader-sync-designed-for-safe-convergence

Status: IN

Multi-leader sync is designed for safe convergence: the two-phase collect-then-distribute pattern prevents intra-round cascading, custom merge functions are required to be idempotent across repeated syncs, and merged results receive fresh timestamps ensuring they supersede both inputs.

Justifications

Three complementary design choices ensure that sync rounds converge monotonically without re-triggering conflicts

Depends on (SL): multi-leader-sync-collects-then-distributes, multi-leader-custom-merge-idempotent-across-syncs, multi-leader-custom-merge-new-timestamp

Depended on by

JSON