# Elasticsearch shows Circuit Breaking Exception

**URL:** https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872
**Category:** Elasticsearch
**Created:** [December 30, 2020, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872 "2020-12-30T10:29:40Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![pavank](https://avatars.discourse-cdn.com/v4/letter/p/f0a364/32.png) [@pavank](https://discuss.elastic.co/u/pavank)
#### Post date: [December 30, 2020, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/1 "2020-12-30T10:29:40Z")

</div>

We have Elasticsearch deployed in a Kubernetes cluster as a 3 node (all 3 are Master and Data).  
Recently we are facing issue with Elasticsearch Circuit breaking excpetion and only 2 nodes are reporting to the Cluster. And the Cluster state is always RED.

 ![Cirucit Breaking Exception](https://us1.discourse-cdn.com/elastic/original/3X/7/7/77db100adfbeb24ff1b2211e7757f13bd23c1e62.png)  
The output for allocation/explain returns:  
{  
"error" : {  
"root\_cause" : [  
{  
"type" : "circuit\_breaking\_exception",  
"reason" : "[parent] Data too large, data for [\<transport\_request\>] would be [6362457143/5.9gb], which is larger than the limit of [5988548608/5.5gb]",  
"bytes\_wanted" : 6362457143,  
"bytes\_limit" : 5988548608  
}  
],  
"type" : "circuit\_breaking\_exception",  
"reason" : "[parent] Data too large, data for [\<transport\_request\>] would be [6362457143/5.9gb], which is larger than the limit of [5988548608/5.5gb]",  
"bytes\_wanted" : 6362457143,  
"bytes\_limit" : 5988548608  
},  
"status" : 503  
}

Can we set the Parent circuit breaker limit value to the required size via ES API?

Regards,  
Pavan

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [December 30, 2020, 10:36am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/2 "2020-12-30T10:36:48Z")

</div>

The circuit breaker is there to prevent nodes from crashing, so I would recommend first looking into what is causing the high heap usage. What is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/cluster-stats.html)? Do you have any non-standard settings that could impact heap usage?

---

<div class="post-metadata">

### Author: ![tusharnemade](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@tusharnemade](https://discuss.elastic.co/u/tusharnemade)
#### Post date: [December 30, 2020, 12:46pm UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/3 "2020-12-30T12:46:56Z")

</div>

Hi

You may implement either of below

1. Increase your Server RAM to have more HEAP\_SIZE

2. You need to adjust `jvm.option` file below parameters and check what values are optimal for your environment.

10-:-XX:G1ReservePercent=25  
10-:-XX:InitiatingHeapOccupancyPercent=30

Thanks  
Tushar Nemade

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 30, 2020, 8:20pm UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/4 "2020-12-30T20:20:28Z")

</div>

> [@tusharnemade](#):
>
> 1. You need to adjust `jvm.option` file below parameters and check what values are optimal for your environment.
> 
> 10-:-XX:G1ReservePercent=25  
> 10-:-XX:InitiatingHeapOccupancyPercent=30

We do not recommend altering these.

---

<div class="post-metadata">

### Author: ![tusharnemade](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@tusharnemade](https://discuss.elastic.co/u/tusharnemade)
#### Post date: [December 31, 2020, 3:12am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/5 "2020-12-31T03:12:37Z")

</div>

Okay.

How to fix this Circuit Breaker issue , if it arrises suddenly after few days of running Elasticsearch v7.x as data to be pushed to ES Index has not increased.

---

<div class="post-metadata">

### Author: ![pavank](https://avatars.discourse-cdn.com/v4/letter/p/f0a364/32.png) [@pavank](https://discuss.elastic.co/u/pavank)
#### Post date: [January 4, 2021, 7:19am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/6 "2021-01-04T07:19:28Z")

</div>

Hello Mark,

I just modified the transient **indices.breaker.total.limit** to the required memory so that the cluster can spin up.  
Once the cluster state turned Green, I have reverted the circuit breaker and restarted my ES nodes.  
Could you help me to avoid this from happening again? Or if it happens again, is there any document that can help me where to look for the error, configurations to consider to troubleshoot this issue faster?

I probably should have mentioned this with the OP, I am using Elasticsearch 6.3.0.

Regards,  
Pavan

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 1, 2021, 7:19am UTC](https://discuss.elastic.co/t/elasticsearch-shows-circuit-breaking-exception/259872/7 "2021-02-01T07:19:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.