Elasticsearch

Circuit Breaker Trips Preventing OOM

warning
Resource ContentionUpdated Mar 2, 2026

Circuit breakers trip to prevent operations that would cause OutOfMemoryError by estimating memory requirements and rejecting requests that exceed configured limits. Frequent trips indicate memory pressure or oversized operations.

How to detect:

elasticsearch.breaker.tripped increasing consistently, with elasticsearch.breaker.memory.estimated approaching elasticsearch.breaker.memory.limit (typically 95% of heap for parent breaker)

Recommended action:

Identify which breaker is tripping via _nodes/stats/breaker API. For request breaker: reduce query complexity, limit aggregation bucket counts, use composite aggregations for high-cardinality fields. For fielddata breaker: enable doc values instead of fielddata, reduce unique term counts in aggregations. For in-flight requests breaker: limit concurrent client connections, implement request queuing at application layer. For parent breaker: overall heap is too small - increase JVM heap size (up to 32GB) or scale horizontally. Review elasticsearch.node.cache.memory.usage and elasticsearch.index.cache.memory.usage for cache pressure. Consider using indices.breaker.total.use_real_memory for more accurate accounting.