ES /docs

Api::V1::Admin::UsersController#assign_editings (avg 15791ms, max 20572ms)

Service
cupixworks-api
Occurrences
53
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
72c89098-3722-46ac-bc36-79d73f9caef0
First Seen
2026-07-01 01:57 UTC
Last Seen
2026-08-03 05:29 UTC
Datadog↗ Slack↗
Actions

Api::V1::Admin::UsersController#assign_editings (avg 15791ms, max 20572ms)

What Happened#

2026-07-01 10:57~11:00 KST 사이 cupixworks-api (production, us-west-2)에서 POST /api/v1/admin/users/:id/assign_editings 요청 2건이 평균 15.8초, 최대 20.6초의 응답 지연을 보였다. 같은 시간대에 여러 다른 컨트롤러(PanosController, CapturesController, JobsController)에서 Mysql2::Error::TimeoutError: Lock wait timeout exceeded 502 에러가 대량으로 발생하고 있었으며, assign_editings의 지연은 이 광범위한 MySQL row lock 경합의 부수적 증상이다.

Quick Facts#

Field Value
resource_name Api::V1::Admin::UsersController#assign_editings
cluster_type latency
avg_duration_ms 15791
max_duration_ms 20572
top_frame app/repositories/concerns/finalization_repository.rb:64 (target_editing.update!(editor_id: user_id))
deploy production-us-west-2-20260701T0155Z0-c527a441-cupixworks (feature 배포 8분 전)
env production, us-west-2
tenant cupix

Affected Teams#

Team / Domain Error Count Impact
Editing / assign_editings 2 편집자(editor)가 작업 할당 요청 시 15~20초 대기 (성공적으로 200 반환)
Panos / Captures / Jobs 컨트롤러 36+ 502s 동일 시간대 광범위한 MySQL LockWaitTimeout로 인해 서비스 저하

Timeline#

  1. 2026-07-01 10:44 KST — 첫 ActiveRecord::LockWaitTimeout 발생 (PUT /api/v1/panos/90876936/stitched). MySQL row lock 경합 시작.
  2. 2026-07-01 10:47 KST — Lock wait timeout이 PanosController, JobsController 등 여러 엔드포인트로 확산.
  3. 2026-07-01 10:48 KST — production-us-west-2-20260701T0148Z0 신규 배포 롤아웃.
  4. 2026-07-01 10:57:28 KST — 클러스터 first_seen: assign_editings 첫 지연 요청.
  5. 2026-07-01 11:00:29 KST — 클러스터 last_seen: 두 번째 지연 요청.
  6. 2026-07-01 11:04 KST — 여전히 Mysql2::Error::TimeoutError 발생 (Api::V1::PanosController#stitched).

Scoring#

Confidence 85% · Actionability 44%

Confidence#

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

Actionability#

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