ES /docs

error on sitetrack_id: 21336 - Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try restarti

Service
cupixworks-worker
Occurrences
1
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
3c4e3657-7afe-4248-9875-25dad33fb02b
First Seen
2026-07-16 13:31 UTC
Last Seen
2026-07-16 13:31 UTC
Actions

error on sitetrack_id: 21336 - Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try restarti

What Happened#

2026-07-16 22:31 KST, cupixworks-workerCreateSitetrackEditingEntitiesWorker#performsitetrack_id=21336 처리 중 Mysql2::Error::TimeoutError: Lock wait timeout exceeded 로 실패했다. 20초 간격으로 동일 sitetrack 에 대해 두 개의 워커가 동시에 시작(22:14:58, 22:15:18)했고, 두 번째 워커가 첫 번째 워커가 보유한 InnoDB row lock 을 획득하지 못한 채 MySQL innodb_lock_wait_timeout 에 걸린 사례이다. 첫 번째 워커는 이후 22:49:47 에 정상 종료되어 실제 편집 엔티티 생성은 완료되었다.

Quick Facts#

Field Value
exception.class Mysql2::Error::TimeoutError
exception.message Lock wait timeout exceeded; try restarting transaction
top_frame app/workers/create_sitetrack_editing_entities_worker.rb:91 (rescue site)
env production, us-west-2
tenant cupix

Affected Teams#

Team / Domain Error Count Impact
cupixworks-worker / editing assignment 1 단일 sitetrack (21336) 처리 실패, 동일 sitetrack 병렬 워커 중 하나만 성공 — 사용자 데이터 손실 없음

Timeline#

  1. 2026-07-16 22:14:58 KST — Worker A: start creating editing entities on sitetrack_id: 21336
  2. 2026-07-16 22:15:18 KST — Worker B: 동일 sitetrack 대상으로 두 번째 perform 시작 (20초 후)
  3. 2026-07-16 22:31:19 KST — Worker B: Mysql2::Error::TimeoutError: Lock wait timeout exceeded 로 rescue 진입, 에러 로그 기록 (start 로부터 ~16분)
  4. 2026-07-16 22:49:47 KST — Worker A: end creating editing entities on sitetrack_id: 21336 정상 종료 (start 로부터 ~34분)

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 2 log queries
Code path explicitness 3/3 15 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 1/5 critical
Affected files 1/5 10 file(s)
Single repo 1/3 2 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