Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency¶
Gray, C. G., & Cheriton, D. R. (1989). Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. ACM, 202-210.
Cited by¶
6 citations across 6 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Escrow or Reservation Hold
- It draws on the same logic as a lease: authority granted for a bounded time that lapses safely if the holder goes silent.
This sourceDefines a lease as a time-bounded grant whose authority expires when its lease period ends unless it is renewed.
- It draws on the same logic as a lease: authority granted for a bounded time that lapses safely if the holder goes silent.
- Lease-Based Resource Hold
- … is that it makes holding self-limiting without anyone having to detect a deadlock or intervene: an absent or dead holder cannot freeze a resource, because the grant evaporates on its own — the classic distributed-systems lease pairs a bounded term with cache- or lock-consistency guarantees for exactly this reason.
This sourceDefines leases as time-bounded grants for cache consistency whose expiration limits the effect of client or communication failure.
- … is that it makes holding self-limiting without anyone having to detect a deadlock or intervene: an absent or dead holder cannot freeze a resource, because the grant evaporates on its own — the classic distributed-systems lease pairs a bounded term with cache- or lock-consistency guarantees for exactly this reason.
- Lease-Bound Capability Token
- Its strength is that it removes the need for a reliable, always-reachable revocation channel — the dominant reason distributed systems reach for leases at all
This sourceUses time-bounded leases so a server can recover without depending on an immediate revocation response: authority expires after the lease term and service can continue once it lapses.
- Its strength is that it removes the need for a reliable, always-reachable revocation channel — the dominant reason distributed systems reach for leases at all
- Reservation-Commit Protocol
- The discipline that keeps it honest is to make every hold lease-bound with automatic expiry
This sourceDefines leases as rights granted for a limited term that expire unless renewed.
- The discipline that keeps it honest is to make every hold lease-bound with automatic expiry
- Stale Edge Expiration
- It works like a lease — a time-bounded grant
This sourceDefines a lease as a grant of specified rights for a limited term that must be extended after expiry.
- It works like a lease — a time-bounded grant
- Timeout Expiration Handler
- The renewable form is precisely a lease
This sourceDefines leases as limited-term rights that can be extended and ensure an unreachable holder delays others only until expiry.
- The renewable form is precisely a lease
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 6 citations of this work carries a recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:9c2605e74db5 · see in the full table