Circuit Breaker Used Is High
Circuit breaker memory use on the listed nodes is sustained near configured limits. You are close to tripping breakers on the next large query or traffic spike.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, memory, stability |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Request circuit breaker threshold percent | Percentage | 10 |
| Field data circuit breaker threshold percent | Percentage | 10 |
| Parent circuit breaker threshold percent | Percentage | 10 |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
The amount of memory used for parent circuit breaker is: 85%
The affected node/s are: es-data-01 and es-data-02
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Review parent circuit breaker
Condition: Always shown for this insight.
Review the parent circuit breaker limit if it is set low and rejects requests before real memory pressure. Increase node heap or raise the limit if your workload needs more headroom.
Increase heap on node
Condition: Shown when heap is smaller than the max recommended.
Current max heap is 30 GB. Set JVM heap to 31 GB (suitable for this machine type), then restart the node.
Impact: As memory usage increases and approaches the circuit breaker limit, the application will start throwing exceptions due to the circuit breakers being tripped. It’s important to review the queries and the memory requirements of the queries to avoid reaching the circuit breaker limit.