ES /docs

flush_geo_coordinate - error - message: Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try

Service
cupixworks-worker
Occurrences
5
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
a4adaa60-a08f-46f5-ae4d-2aba5b113484
First Seen
2026-04-23 08:15 UTC
Last Seen
2026-07-10 18:29 UTC
Actions

flush_geo_coordinate - error - message: Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try

What Happened#

2026-04-23 08:1508:34 UTC (KST 17:1517:34) 사이에 cupixworks-worker 서비스의 flush_geo_coordinate 메서드에서 MySQL Lock wait timeout exceeded 에러가 2건 발생했다. 동일 시간대에 다수의 flush_geo_coordinate 작업이 동시 실행되면서 records 테이블의 행 잠금 경합이 발생한 것이 원인이다.

Quick Facts#

Field Value
exception.class Mysql2::Error::TimeoutError
exception.message Lock wait timeout exceeded; try restarting transaction
top_frame app/models/concerns/record_geo_coordinate.rb:83
env production, us-west-2

Timeline#

  1. 2026-04-23 08:10~08:20 UTC — 10분간 20건 이상의 flush_geo_coordinate - begin 로그 관측. 다수 worker가 동시에 flush 작업 수행 중.
  2. 2026-04-23 08:15:15 UTC — 첫 번째 Lock wait timeout exceeded 에러 발생.
  3. 2026-04-23 08:17:57 UTC — 동일 시간대에 PullTaskWorker에서도 Lock wait timeout exceeded 에러 발생 (records 테이블 경합 확산).
  4. 2026-04-23 08:34:17 UTC — 두 번째 Lock wait timeout exceeded 에러 발생.
  5. 2026-04-23 08:34 UTC 이후 — 경합 자연 해소. 이후 flush 작업은 정상 완료.

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 14 code refs, 5 log queries
Code path explicitness 3/3 14 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