tech-log-backend/docs/runbooks/lock-acquisition-timeout.md

title, category, error_codes, severity, owner, last_updated, status

title	category	error_codes	severity	owner	last_updated	status
Runbook — LOCK_ACQUISITION_TIMEOUT (분산 락 획득 타임아웃)	CONFLICT	LOCK_ACQUISITION_TIMEOUT	P2	oncall	2026-06-15	stub

Runbook: LOCK_ACQUISITION_TIMEOUT (runbook://lock/acquisition-timeout)

Symptoms

• HTTP 409 with error.code=LOCK_ACQUISITION_TIMEOUT
• Distributed lock wait exceeded configured timeout; high contention on a resource

Diagnosis

• Check lock.acquisition metric for lock name and duration
• Identify lock holders (check DB integration_lock table)

Action

• Client should retry with backoff (retryable=true)
• Optimize critical section holding time if lock contention is systemic

Escalation

• Escalate if lock holder appears stuck (potential deadlock in distributed lock)

---

Stub: Phase D2 — author body after domain adoption. (feature-operational-runbook-contract D9)