AnalyzePanoWorker::perform | error on 737963 - Mysql2::Error::TimeoutError: Lock wait timeout exceed

What Happened#

2026-07-18 15:04 KST, cupixworks-worker(production, us-west-2)의 AnalyzePanoWorker::perform가 capture 737963에서 Mysql2::Error::TimeoutError: Lock wait timeout exceeded로 실패했다. 오류는 1회 발생했고 Sidekiq 자동 재시도(retry: 1)로 15:04:27 KST에 재시도가 성공하여 15:06:53 KST에 정상 완료됐다. 최종 사용자 영향은 없다.

Quick Facts#

Affected Teams#

Timeline#

1. 2026-07-18 15:02:35 KST — Capture 737963에서 run_3d_reconstruction? 검증 시작 (Capture#run_3d_reconstruction?)
2. 2026-07-18 15:02:49 KST — Reconstruction 잡 생성 (job_id 1208310), CaptureInvoker#create_3d_reconstruction
3. 2026-07-18 15:02:55 KST — AnalyzePanoWorker::perform | begins on 737963 (1차 실행)과 동시에 Capture 737963 processing is completed (Capture#notify_processing_completed), Capture intelligence job 생성 (job_id 1208311)
4. 2026-07-18 15:04:03 KST — AnalyzePanoWorker::perform가 Mysql2::Error::TimeoutError: Lock wait timeout exceeded로 실패 (begins로부터 68초 경과 → InnoDB innodb_lock_wait_timeout 대기 후 타임아웃 추정)
5. 2026-07-18 15:04:13 KST — reconstruction_state has transitioned from none to queued on Capture 737963
6. 2026-07-18 15:04:19 KST — update_associated_sitetracks, update_associated_deviations 실행
7. 2026-07-18 15:04:25 KST — Reconstruction/Capture Intelligence SQS 메시지 전송
8. 2026-07-18 15:04:27 KST — Sidekiq 재시도로 AnalyzePanoWorker::perform | begins on 737963 (2차 실행)
9. 2026-07-18 15:04:47 KST — AnalyzePano::analyze | capture_id=737963 total_panos=297
10. 2026-07-18 15:06:53 KST — AnalyzePanoWorker::perform | uploaded and waiting callback on 737963 (재시도 성공)

Scoring#

Confidence 80% · Actionability 44%

Confidence#

Actionability#