Geo-Replication Conflict / Divergence
Write conflicts and data divergence that occur in active-active geo-replicated object storage when multiple sites independently write to the same object key or modify the same metadata.
Summary
Write conflicts and data divergence that occur in active-active geo-replicated object storage when multiple sites independently write to the same object key or modify the same metadata.
Geo-replication conflicts are the fundamental challenge of multi-site object storage. The CAP theorem guarantees that active-active replication across WAN links must choose between consistency and availability — and most object storage systems choose availability, accepting temporary divergence.
- Last-writer-wins (LWW) is the most common conflict resolution but can silently drop writes. Applications that cannot tolerate lost writes need application-level conflict handling.
- Replication lag is not the same as conflict. Lag is temporary inconsistency that resolves; conflicts require explicit resolution. Monitoring must distinguish between the two.
- CRDT
solvesGeo-Replication Conflict / Divergence — coordination-free convergence - Active-Active Multi-Site Object Replication
constrained_byGeo-Replication Conflict / Divergence scoped_toGeo / Edge Object Storage, Object Storage
Definition
Write conflicts and data divergence that occur when the same object key is modified at multiple sites simultaneously in an active-active geo-replicated object store.
Connections 5
Outbound 3
Inbound 2
solves1constrained_by1Resources 2
S3 replication documentation covering cross-region replication semantics, conflict resolution, and replication time control.
Ceph multi-site replication documentation covering eventual consistency, conflict resolution, and zone synchronization.