Quorum lease
A quorum lease lets designated Paxos replicas read leased objects locally while requiring synchronous notification before updates commit.
Grantors and holders are different sets: activation needs majority-backed promises, but the holder set can have any size. Accepted-but-unresolved commands must be settled before local reads. [1]
A multi-object write needs acknowledgements from the union of its objects' holder sets, as well as a Paxos majority. Separate majority-sized leases can therefore require all replicas for a combined write. [1]
Set example: among replicas 0-4, holders {0,1,2} and {0,3,4} cover all five. Enumerating the six three-member holder sets containing replica 0 gives 36 ordered pairs: 6 unions of size three, 24 of size four and 6 of size five. These are equally enumerated configurations, not workload probabilities. [2]
A composite local read requires active leases for every queried object and atomic execution at one holder; otherwise it follows the Paxos path. The reported experiments covered single-object operations. [1]
Relations
- related
- Paxos, Quorum intersection
Limitations
- An unavailable holder can delay affected writes until promises expire; clock-rate drift must remain within the timing guard. [1]
Citations
- Moraru, Andersen and Kaminsky. Paxos Quorum Leases: Fast Reads Without Sacrificing Writes. SoCC 2014, sections 3 and 5.
- Hesela: exact holder-set union enumeration (JavaScript source, Node.js)
Further reading
Sources & caveats
- The SoCC 2014 paper describes a research protocol. This record combines source synthesis with exact set arithmetic, not a distributed-system experiment.