ES /docs

Index error - [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to p

Service
cupixworks-api
Occurrences
16,947
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
d393c5d7-73d2-4f68-b52b-9738f632c361
First Seen
2026-05-22 04:00 UTC
Last Seen
2026-07-22 16:28 UTC
Actions

Index error - [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to p

What Happened#

2026-05-22 04:0004:43 UTC 사이에 cupixworks-api 서비스에서 ElementTrace를 Elasticsearch에 인덱싱하는 과정에서 mapper_parsing_exception 에러가 6,356회 발생했다. BIM 좌표계의 값을 geo_point의 latitude/longitude로 직접 사용하면서, 유효 범위(-9090)를 벗어나는 값(예: 2139310, -167596)이 Elasticsearch에 전달되어 거부되었다.

Quick Facts#

Field Value
exception.class Elasticsearch::Transport::Transport::Errors::BadRequest
exception.message mapper_parsing_exception: failed to parse field [location] of type [geo_point]
top_frame app/models/concerns/searchable.rb:51 (Index error), app/models/concerns/searchable.rb:116 (ElasticsearchError)
env production, us-west-2

Timeline#

  1. 2026-05-22T04:00:01Z — 최초 에러 발생 (ElementTrace._index_document)
  2. 2026-05-22T04:43:07Z — 마지막 에러 기록
  3. 2026-05-22T05:00:00Z — Error Sweeper 수집

Scoring#

Confidence 85% · Actionability 28%

Confidence#

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