ES /docs

CaptureRepository#update — InnoDB row-lock timeout

Service
cupixworks-api
Occurrences
3
Status
Pr_created
Confidence
95%
Actionability
52%
Cluster ID
be196c4b-4151-49c7-acac-99be79e4e5ed
First Seen
2026-05-29 01:58 UTC
Last Seen
2026-07-03 08:57 UTC
Datadog↗ Slack↗ TSLA-13049↗ PR · tesla↗
Actions
현재 상태 pr_created 에서는 실행할 액션이 없습니다.

CaptureRepository#update — InnoDB row-lock timeout

What Happened#

2026-05-29 10:58 KST, eu-central-1 리전에서 Api::V1::Admin::CapturesController#update 요청이 MySQL InnoDB lock wait timeout(50초)에 도달하여 502 응답을 반환했다. 동일 시간대에 EditingsController#update에서도 반복적인 lock wait timeout이 발생하고 있어, 동시 트랜잭션 간 row-level lock 경합이 원인으로 확인되었다.

Quick Facts#

Field Value
exception.class ActiveRecord::LockWaitTimeout
exception.message Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try restarting transaction
top_frame app/repositories/admin/capture_repository.rb:38
env production, eu-central-1
resource_name Api::V1::Admin::CapturesController#update
duration 50,048ms (DB: 50,016ms)
http_status 502

Affected Teams#

Team / Domain Error Count Impact
Admin Operations (editing) 2 capture 37119 업데이트 실패, 관리자 작업 차단
Editing Pipeline 13+ editing 121538 상태 전환 반복 실패 (01:34~01:45)

Timeline#

  1. 2026-05-29 10:22 KST — Capture 37119에 대해 3D Reconstruction invoked on publish
  2. 2026-05-29 10:24 KST — Capture 37119 unpublish 수행
  3. 2026-05-29 10:34 KST — Editing 121538에서 lock wait timeout 시작 (EditingsController#update)
  4. 2026-05-29 10:45 KST — Editing 121538 lock wait timeout 반복 종료 (13+ 건)
  5. 2026-05-29 10:59 KST — Admin::CapturesController#update capture 37119 요청 → lock wait timeout (50s), 502 반환
  6. 2026-05-29 11:02 KST — 동일 요청 재시도 → 동일 lock wait timeout (50s), 502 반환
  7. 2026-05-29 11:02 KST — error-sweeper 감지

Scoring#

Confidence 95% · Actionability 52%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 27 code refs, 4 log queries
Code path explicitness 3/3 27 file:line refs
Log evidence 3/3 section, query, pattern
RCA structure 3/3 3/3 sections
Revision history 2/3 2 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 31 file(s)
Single repo 1/3 2 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 3/3 no external deps
Data migration 3/3 no migration