ES /docs

voxel-service Athena polling infinite loop — API Gateway timeout

Service
cupixvista-api-worker
Occurrences
1,873
Status
Reported
Confidence
85%
Actionability
32%
Cluster ID
6ce69bd3-ce90-440d-aabc-ad39e2720779
First Seen
2026-07-13 08:33 UTC
Last Seen
2026-08-05 04:52 UTC
Actions

voxel-service Athena polling infinite loop — API Gateway timeout

What Happened#

2026-07-13 17:35~17:40 KST 사이 cupixvista 프로덕션(us-west-2) Sidekiq 워커에서 Cupix::VoxelService.captured_area! 가 voxel-service Lambda(PUT /api/v1/voxels/captured_area) 호출 중 HTTP 500 을 받아 2건의 error 가 기록되었다. 대상은 Facility ID 8(facility_key=3ok09a)와 Facility ID 15(facility_key=yf8szb). 두 요청 모두 Athena 쿼리 자체는 발행됐지만 state: 로그가 남지 않아 Lambda 가 API Gateway 통합 타임아웃(30s) 을 넘긴 채 실행되고 있었음이 확인된다.

Quick Facts#

Field Value
exception.class Cupix::Errors::System (code SYS20000)
exception.message failed to get captured area - error: 500 Internal Server Error
top_frame app/services/cupix/voxel_service.rb:99
runtime ruby/3.3.7 (rest-client/2.1.0)
deploy production-us-west-2-20260713T0831Z0-69260da5-cupixvista
env production, us-west-2, tenant cupix (cupixvista 배포)

Affected Teams#

Team / Domain Error Count Impact
cupixvista-api-worker (VoxelService / Facility) 2 Facility 2개(ID 8, 15)의 captured_size / FootprintHistory 갱신 실패 — UI 에 표시되는 촬영 면적 수치가 오래된 값으로 남음

Timeline#

  1. 2026-07-13 17:33 KST — Facility 8 (3ok09a) 에 대한 첫 PUT /api/v1/voxels/captured_area 요청 발행 (trace 2180691606340267128).
  2. 2026-07-13 17:33~17:35 KST — 동일 facility 로 3회 추가 호출 발행. 각 호출에서 ALTER TABLE ADD PARTITION 쿼리는 SUCCEEDED 로 완료됐지만, 본 SELECT 쿼리(67074fbb..., b11aa3d1..., ede2cf07..., 539bf4f0...)는 이후 state: 로그가 남지 않음.
  3. 2026-07-13 17:35:34 KSTCupix::VoxelService.captured_area! 가 500 을 수신 → SYS20000 발생 → Facility#calculate_captured_size rescue 에서 로깅 (Facility ID 8).
  4. 2026-07-13 17:39~17:40 KST — Facility 15 (yf8szb) 로 동일 패턴 반복.
  5. 2026-07-13 17:40:48 KST — Facility 15 에 대해 동일한 500 에러 발생. 이후 재발 로그 없음.

Scoring#

Confidence 85% · Actionability 32%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 4 log queries
Code path explicitness 3/3 11 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 18 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 0/3 migration needed