What causes OpenSearch 429 errors from a sort query?

Circuit breakers tripping on fielddata heap overload, often from sorting metadata like _id without doc values.

How to safely sort by document ID in OpenSearch?

Map a keyword field with doc_values:true (or .keyword subfield), sort on that instead of _id.

Doc values always — on-disk, efficient. Fielddata's a heap hog, avoid at scale.

One field in a sort query. That's all it took to push our OpenSearch cluster to the brink. JVM at 99%, errors everywhere — a classic prod nightmare.

theAIcatchup Apr 10, 2026 3 min read

Never sort on _id or metadata fields without doc values — use a mapped keyword instead. 𝕏
Doc values (disk, index-time) beat fielddata (heap, query-time) for production sorts and aggs. 𝕏
Monitor JVM heap and fielddata cache; they're early warnings for sort-induced outages. 𝕏

Published by

Ship faster. Build smarter.

#OpenSearch #_id sort #cluster outage #doc values #fielddata

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to