inconsistent-replication · research · also IR replication

Inconsistent replication

Inconsistent replication is a fault-tolerant protocol that preserves an unordered operation set while leaving application-level ordering and conflict decisions to a higher layer.

Related Observatory article: Read on hesela.com

Modes: Inconsistent operations preserve operations; consensus operations also preserve a selected result, subject to the protocol's application Merge rules. Neither mode imposes a total execution order. TAPIR supplies the transaction semantics. [1]

Implementation: The client groups replies by view and replica identity. A fast-path result needs f+ceil(f/2)+1 matching replies; otherwise the slow path selects a result and waits for finalization acknowledgements. [3] [2]

Assumptions: The paper uses 2f+1 replicas and at most f simultaneous crash failures, not Byzantine failures or arbitrary loss of all replicas. Application invariants and recovery functions must satisfy the IR interface; IR is not a drop-in replacement for an ordered log. [1]

Relations

related
TAPIR

Citations

  1. Zhang et al. Building Consistent Transactions with Inconsistent Replication. SOSP 2015, pp. 263-278; DOI 10.1145/2815400.2815404, sections 3-6. (accessed 2026-11-16)
  2. UWSysLab TAPIR configuration.cc: QuorumSize and FastQuorumSize, commit c50d906 (accessed 2026-11-16)
  3. UWSysLab TAPIR IR client.cc: matching results, slow path and finalization, commit c50d906 (accessed 2026-11-16)
Sources & caveats
  • Full-paper and pinned-code review. No prototype execution, performance reproduction or formal verification. The inspected repository revision is not identified as the evaluated 2015 artifact.

JSON: /data/terms/inconsistent-replication.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Inconsistent replication. Hesela. 2026-11-16. https://hesela.dev/terms/inconsistent-replication/