ES /docs

ElasticsearchError - [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"fail

Service
cupixworks-api
Occurrences
16,943
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
b18a125e-4f02-46b8-b3d9-823a1518d4e8
First Seen
2026-05-22 04:00 UTC
Last Seen
2026-05-27 04:51 UTC
Actions

ElasticsearchError - [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"fail

What Happened#

2026-05-22 04:0004:43 UTC 사이에 cupixworks-api 서비스에서 ElementTrace를 Elasticsearch에 인덱싱할 때 mapper_parsing_exception 에러가 6,356건 발생했다. BIM 좌표계의 center point 값(예: latitude 2139310.163528784)이 유효한 geo_point 위도 범위(-9090)를 초과하여 ES가 문서 인덱싱을 거부한 것이 원인이다.

Quick Facts#

Field Value
exception.class Elasticsearch::Transport::Transport::Errors::BadRequest
exception.message [400] mapper_parsing_exception: failed to parse field [location] of type [geo_point] - illegal latitude value
top_frame app/models/concerns/searchable.rb:116
env production, us-west-2
deploy production-us-west-2-20260521T1035Z0-3e770a15-cupixworks

Affected Teams#

Team / Domain Error Count Impact
clark-vdc (team 87) ~5000+ ElementTrace ES 검색 인덱스 미동기화
ellisdon (team 268) ~1000+ ElementTrace ES 검색 인덱스 미동기화

Timeline#

  1. 2026-05-22T04:00:01Z — 최초 에러 발생 (facility_key: 3fq7tj, team clark-vdc)
  2. 2026-05-22T04:04:49Z — 다수 사용자에서 동시 다발적 에러 (facility_key: 3fq7tj, rkuup2)
  3. 2026-05-22T04:43:07Z — 마지막 에러 기록
  4. 2026-05-22T05:00:00Z — Error Sweeper 감지

Scoring#

Confidence 85% · Actionability 28%

Confidence#

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