TAPIR
TAPIR is a distributed transaction protocol that combines optimistic validation with inconsistent replication to provide strictly serializable committed transactions.
Layers: Prepare uses IR consensus operations; Commit and Abort use inconsistent operations. A client coordinates participating shards, so no replication leader does not mean no transaction coordinator. [1]
Fast path: The pinned IR client requires matching results from a fast quorum in one view, not just enough replies. Missing that condition takes a slow path with finalization; it does not itself mean transaction abort. [3]
Three replicas: For f=1 and n=2f+1, the code requires three matching fast-path replies versus two for a normal quorum. One unavailable replica removes this fast path without exceeding the modeled failure budget. [2]
Scope: One-round-trip commit excludes earlier reads and later asynchronous work. This is not a universal transaction-latency or power-loss guarantee. [1]
Relations
Citations
- Zhang et al. Building Consistent Transactions with Inconsistent Replication. SOSP 2015, pp. 263-278; DOI 10.1145/2815400.2815404, sections 3-6.
- UWSysLab TAPIR configuration.cc: QuorumSize and FastQuorumSize, commit c50d906
- UWSysLab TAPIR IR client.cc: matching results, slow path and finalization, commit c50d906
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.