{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-23",
  "slug": "lock-delay",
  "term": "Lock-delay",
  "aliases": [
    "Lock reacquisition delay"
  ],
  "definition": "Lock-delay postpones reacquisition of a lock after its holder or associated session is invalidated.",
  "note": "The delay is a coordination safeguard, not a storage-side rejection of old requests. A 2006 lock-service design applies it after holder failure or loss of contact, while normal release permits immediate reacquisition. Its one-minute cap limits unavailability rather than delayed-I/O lifetime. [lock-service-osdi06]\n\nIn Consul, TTL-based expiry has a lower bound; critical health check or explicit destruction can invalidate the session earlier. Lock-delay begins after invalidation. ACL-authorized clients can still perform ordinary KV writes without owning the lock: the delay restricts reacquisition, not all modifications. External storage needs its own enforcement. [session-design]",
  "related": [
    "fencing-token",
    "io-fencing"
  ],
  "citations": [
    {
      "id": "lock-service-osdi06",
      "title": "Mike Burrows. The Chubby lock service for loosely-coupled distributed systems. OSDI 2006, section 2.4.",
      "url": "https://www.usenix.org/legacy/event/osdi06/tech/full_papers/burrows/burrows.pdf",
      "accessed": "2026-10-23"
    },
    {
      "id": "session-design",
      "title": "HashiCorp Consul: Sessions and distributed locks overview, Session Design and K/V Integration.",
      "url": "https://developer.hashicorp.com/consul/docs/automate/session",
      "accessed": "2026-10-23"
    },
    {
      "id": "session-api",
      "title": "HashiCorp Consul: Session HTTP API, Create Session, LockDelay field.",
      "url": "https://developer.hashicorp.com/consul/api-docs/session",
      "accessed": "2026-10-23"
    },
    {
      "id": "hesela-fencing",
      "title": "Hesela: Storage fencing, delayed writes and takeover timing.",
      "url": "https://hesela.com/analyses/storage-fencing-stale-writes/",
      "accessed": "2026-10-23"
    }
  ],
  "provenance": [
    "Historical mechanism from Chubby OSDI 2006 section 2.4; it is not a current service-default claim or a cluster benchmark. [lock-service-osdi06]",
    "Consul overview and API pages read 2026-10-23 disagree on allowing zero LockDelay. No zero-setting recommendation or live-service result is asserted. [session-design] [session-api]"
  ]
}