ES /docs

Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root_cause":[{"type":"x_content_parse_exceptio

Service
cupixvista-elasticsearch
Occurrences
13
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
224ceeff-b748-48c5-992e-138e5a822ff3
First Seen
2025-04-09 09:33 UTC
Last Seen
2026-08-02 18:32 UTC
Datadog↗ Slack↗
Actions

Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root_cause":[{"type":"x_content_parse_exceptio

What Happened#

GET /api/v1/reviews (Api::V1::ReviewsController#index) 요청에서 Elasticsearch 가 [400] BadRequest 를 반환하고, 이것이 Rails 에서 502 로 응답되었다. 클러스터의 Representative Error 는 geo distance must be greater than zero (filter 파싱 실패) 였으나, 이는 STALE 하다. last_seen (2026-08-02) 부근의 실제 최근 로그(2026-08-03)는 다른 메시지 — [multi_match] unknown token [START_OBJECT] after [query] (failed to parse field [must]) — 를 보여준다. 두 변형 모두 클라이언트가 잘못된 형태의 검색 파라미터를 보내 Elasticsearch 쿼리 파싱이 실패한 사례이며, 관측된 최근 요청은 모두 env:dev, user_agent: curl/8.7.1 의 수동 호출이다.

Quick Facts#

Field Value
exception.class Elasticsearch::Transport::Transport::Errors::BadRequest
exception.message (recent) [400] {"error":{"root_cause":[{"type":"parsing_exception","reason":"[multi_match] unknown token [START_OBJECT] after [query]","line":1,"col":666}],"type":"x_content_parse_exception","reason":"[1:666] [bool] failed to parse field [must]"},"status":400}
exception.message (representative, stale) [400] ... "[bool] failed to parse field [filter]" ... "distance must be greater than zero"
top_frame lib/cupix/query_option/base.rb:157-165 (set_search_string → multi_match)
endpoint GET /api/v1/reviews → Api::V1::ReviewsController#index
env dev (us-west-2)
deploy tesla develop (본 조사 시점 790e093bb)

Affected Teams#

Team / Domain Error Count Impact
cupixworks-api (Api::V1::ReviewsController#index) 14 (누적, 여러 변형 그룹핑) 잘못된 검색 파라미터를 보낸 개별 요청만 502 반환. 관측된 최근 요청은 dev 환경의 curl 수동 호출

Timeline#

  1. 2025-04-09 18:33 KST — 이슈 first_seen (Representative Error: geo distance must be greater than zero, stale)
  2. 2026-08-03 11:47 KST — 실제 최근 발생 (multi_match / START_OBJECT after [query], env=dev, curl/8.7.1)
  3. 2026-08-03 12:20 KST — 동일 패턴 재발 (동일 user_agent/env)
  4. 2026-08-04 — RCA 분석. last_seen 부근 로그 기준으로 root cause 재확정

Scoring#

Confidence 85% · Actionability 44%

Confidence#

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