--- title: Runbook — LOCK_ACQUISITION_TIMEOUT (분산 락 획득 타임아웃) category: CONFLICT error_codes: [LOCK_ACQUISITION_TIMEOUT] severity: P2 owner: oncall last_updated: 2026-11-07 status: stub --- # Runbook: LOCK_ACQUISITION_TIMEOUT (`runbook://lock/acquisition-timeout`) ## Symptoms - HTTP 409 with `error.code=LOCK_ACQUISITION_TIMEOUT` and `Retry-After: 1`; GraphQL extension `code=LOCK_ACQUISITION_TIMEOUT`, gRPC trailer `error-code: LOCK_ACQUISITION_TIMEOUT` (`ABORTED`), all `retryable=true`. A 4xx answer, so no server ERROR line — look at the metric. - Before 2026-11-07 the template answered this as 500 `INTERNAL_ERROR` with an "unhandled exception" ERROR line (the exception was not an `ApiErrorCarrier`). A service on an older template sees that instead. - 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)