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.
Recent developments
- Three-strategy hierarchy: CRDT (strongest), MVCC, Last-Writer-Wins (simplest). 2026 conflict-resolution decision tree consolidates around three approaches — CRDTs deliver causal consistency + strong eventual consistency for application-meaningful state; MVCC for transactional shapes; LWW for simple cases. Pick by data semantics, not infrastructure default. Per InfoQ — Picking an Active-Active Geo Distribution Strategy: Comparing Merge Replication and CRDT.
- Ceph RGW ships conflict-resolution sync log + error codes. Ceph's multi-site replication exposes a structured conflict log with specific error codes + markers — operators can apply custom resolution logic based on object metadata, modification times, or app-specific rules. Production-grade conflict observability beyond LWW. Per OneUptime — How to Set Up Ceph Multi-Site Replication for Geo-Redundancy.
- "If you can't design a deterministic merge strategy, use single-primary." 2026 hard-won wisdom: multi-primary replication only works if the application has a deterministic merge strategy. If conflicts are application-meaningful + need human resolution, drop back to single-primary + accept the failover latency.
- CRDTs deliver "strong eventual consistency" — convergent without coordination. Mathematically proven property: any two replicas seeing the same set of operations converge to the same state regardless of order. The structural advantage over LWW is the elimination of timestamp-ordering paradoxes (clock skew, partition-induced re-ordering). Per InfoQ — Merge Replication and CRDT.
- Redis active-active geo-replication as 2026 reference implementation. Redis's active-active geo-rep ships CRDT-based conflict resolution + automatic replication across all regions. Practitioners are increasingly using Redis as the conflict-resolved metadata layer over plain S3 — the storage layer doesn't need to solve conflict resolution if a higher tier does. Per OneUptime — How to Implement Active-Active Geo-Replication with Redis.
- IBM Storage Defender ships explicit conflict-resolution rule frameworks. IBM's enterprise storage replication ships structured conflict-resolution rules — last-writer-wins, source-wins, target-wins, manual-resolution-queue — exposed as configuration rather than buried in implementation. The "make conflict resolution a configurable policy" pattern is increasingly the enterprise default. Per IBM Docs — Replication Conflict Resolution.
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.