# Circuit Breaking Exception

**URL:** <https://discuss.elastic.co/t/circuit-breaking-exception/148555>\
**Category:** Elasticsearch\
**Created:** [September 14, 2018, 5:20am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555 "2018-09-14T05:20:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nitish\_Goyal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nitish_goyal/32/54988_2.png) [@Nitish\_Goyal](https://discuss.elastic.co/u/Nitish_Goyal)\
**Post date:** [September 14, 2018, 5:20am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555/1 "2018-09-14T05:20:28Z")

</div>

I have recently migrated the cluster from 2.4 to 6.3.0 and I am getting circuit breaking exception every few hours on the nodes

Cluster details -  
Data nodes : 13  
Master nodes : 3  
Query nodes : 3

We aren't using this cluster for searching in production as of now. Only indexing is happening on this cluster  
{  
"type" : "failed\_node\_exception",  
"reason" : "Failed node [YMekd6kcQPydIHKnORSX6g]",  
"caused\_by" : {  
"type" : "circuit\_breaking\_exception",  
"reason" : "[parent] Data too large, data for [\<transport\_request\>] would be [6608475256/6.1gb], which is larger than the limit of [6608348774/6.1gb]",  
"bytes\_wanted" : 6608475256,  
"bytes\_limit" : 6608348774  
}  
}

Heap size is 31 GB  
I have overwritten this setting : indices.breaker.total.limit: 20%  
With the same settings, indexing is working fine in 2.4.0, but failing in 6.3.0

Is this a bug in 6.3.0 version?

Thanks,  
Nitish

---

<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:** [September 14, 2018, 5:45am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555/2 "2018-09-14T05:45:33Z")

</div>

Given the limit you have in place this seems expected. It sounds more like an issue with Elasticsearch 2.4 not triggering circuit breakers correctly. Why have you set `indices.breaker.total.limit` to such a low value?

---

<div class="post-metadata">

**Author:** ![Nitish\_Goyal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nitish_goyal/32/54988_2.png) [@Nitish\_Goyal](https://discuss.elastic.co/u/Nitish_Goyal)\
**Post date:** [September 14, 2018, 6:28am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555/3 "2018-09-14T06:28:11Z")

</div>

Thanks for the explanation

I have set the value to 50% and restarted the failed nodes

Will post it here if I face this issue again

Thanks,  
Nitish

---

<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:** [September 14, 2018, 6:34am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555/4 "2018-09-14T06:34:03Z")

</div>

Why are you overriding this in the first place? Why not use the default value?

---

<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:** [October 12, 2018, 6:34am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/148555/5 "2018-10-12T06:34:04Z")

</div>

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