ES /docs

Post-split cap still exceeded after max re-split retries, giving up

Service
cupixworks-worker
Occurrences
8
Status
Reported
Confidence
85%
Actionability
36%
Cluster ID
2257cf48-732b-466c-b894-5b2e2e009a5f
First Seen
2026-07-09 06:04 UTC
Last Seen
2026-07-09 06:10 UTC
Actions

Post-split cap still exceeded after max re-split retries, giving up

What Happened#

2026-07-09 15:04 KST부터 15:10 KST 사이에 cupixworks-worker (us-west-2 production)에서 Cupix::EditingSplitService#split!가 4개 siteinsights editing (1178504, 1177289, 1186375, 1202324)에 대해 재분할(re-split) 루프에 빠져 각 editing이 MAX_RESPLIT_RETRIES=10 상한을 초과하며 error 로그 8건이 발생했다. 각 editing은 ElementTrace 기준 element 수가 cap(1000)을 크게 초과(1246~6540)하지만, 연결된 EditingEntity(Task) 행이 하나도 남아 있지 않은 orphan ET 상태였다.

Quick Facts#

Field Value
exception.class (no exception raised — Cupix::Logger.error call)
exception.message Post-split cap still exceeded after max re-split retries, giving up
top_frame app/services/cupix/editing_split_service.rb:111
deploy production-us-west-2-20260709T0602Z0-6eb3f711-cupixworks
env production, us-west-2
tenant cupix
affected editing_ids 1178504, 1177289, 1186375, 1202324 (all task_count=0)

Affected Teams#

Team / Domain Error Count Impact
siteinsights (SQA editing pipeline) 8 4개 siteinsights editing이 cap을 초과한 채 :waiting 상태로 남아 후속 QA workflow 진행 불가

Timeline#

  1. 2026-07-09 15:04:52 KST — 4개 editing에 대한 첫 번째 "giving up" error 4건 동시 발생 (모두 resplit_count=10에 도달) — first_seen
  2. 2026-07-09 15:07:28 KST — editing 1178504 재시도 후 다시 error (post_split_count=6540)
  3. 2026-07-09 15:08:32 KST — editing 1177289 다시 error (post_split_count=5880)
  4. 2026-07-09 15:09:46 KST — editing 1186375 다시 error (post_split_count=3630)
  5. 2026-07-09 15:10:20 KST — editing 1202324 다시 error (post_split_count=1246) — last_seen

Scoring#

Confidence 85% · Actionability 36%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 5 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 1/5 critical
Affected files 1/5 8 file(s)
Single repo 1/3 2 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 3/3 no external deps
Data migration 3/3 no migration