# Circuit\_breaking\_exception

**URL:** https://discuss.elastic.co/t/circuit-breaking-exception/247637
**Category:** Elasticsearch
**Created:** [September 5, 2020, 3:10pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637 "2020-09-05T15:10:43Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)
#### Post date: [September 5, 2020, 3:10pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/1 "2020-09-05T15:10:43Z")

</div>

We recently upgraded our elastic **cloud** deployment from 6.8.5 to 7.9  
After the upgrade we are seeing the following error time to time.

```
{
  "error" : {
    "root_cause" : [
      {
        "type" : "circuit_breaking_exception",
        "reason" : "[parent] Data too large, data for [<http_request>] would be [416906520/397.5mb], which is larger than the limit of [408420352/389.5mb], real usage: [416906520/397.5mb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=32399/31.6kb, in_flight_requests=0/0b, model_inference=0/0b, accounting=4714192/4.4mb]",
        "bytes_wanted" : 416906520,
        "bytes_limit" : 408420352,
        "durability" : "PERMANENT"
      }
    ],
    "type" : "circuit_breaking_exception",
    "reason" : "[parent] Data too large, data for [<http_request>] would be [416906520/397.5mb], which is larger than the limit of [408420352/389.5mb], real usage: [416906520/397.5mb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=32399/31.6kb, in_flight_requests=0/0b, model_inference=0/0b, accounting=4714192/4.4mb]",
    "bytes_wanted" : 416906520,
    "bytes_limit" : 408420352,
    "durability" : "PERMANENT"
  },
  "status" : 429
}

```

This deployment consists of only one node with 1G memory. We would like to know the cause of this error. Is it due to the upgrade?

Thank you.

---

<div class="post-metadata">

### Author: ![Imma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/imma/32/32013_2.png) [@Imma](https://discuss.elastic.co/u/Imma)
#### Post date: [September 5, 2020, 5:58pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/2 "2020-09-05T17:58:50Z")

</div>

Yes, Elasticsearch 7.x has several improvements for node resiliency, you can find details here: [https://www.elastic.co/blog/improving-node-resiliency-with-the-real-memory-circuit-breaker](https://www.elastic.co/blog/improving-node-resiliency-with-the-real-memory-circuit-breaker)

I hope this helps!

---

<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: [September 7, 2020, 12:16am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/3 "2020-09-07T00:16:16Z")

</div>

Where are you seeing this, Kibana?

---

<div class="post-metadata">

### Author: ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)
#### Post date: [September 7, 2020, 11:11am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/4 "2020-09-07T11:11:27Z")

</div>

Hi,  
I see this error when I issue a simple curl command to any of the indices.  
Regards,  
Sajeeva.

---

<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: [September 7, 2020, 8:54pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/5 "2020-09-07T20:54:01Z")

</div>

What is the request?

---

<div class="post-metadata">

### Author: ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)
#### Post date: [September 8, 2020, 9:58am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/6 "2020-09-08T09:58:52Z")

</div>

Almost all queries. Even for something like this

`curl -X GET <url>/index_name`

---

<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 8, 2020, 10:01am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/7 "2020-09-08T10:01:22Z")

</div>

You seem to have a very small heap. How much data do you have in the cluster?

---

<div class="post-metadata">

### Author: ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)
#### Post date: [September 9, 2020, 2:10pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/8 "2020-09-09T14:10:30Z")

</div>

Data size is close to 1G.  
Yes, memory utilization is very high, but we did not receive this error when we were on 6.8.5. We started seeing these after upgrading to 7.9

---

<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 9, 2020, 5:01pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/9 "2020-09-09T17:01:19Z")

</div>

Which exact version are you on? I recall reading something about a memory leak in 7.9.0 that I believe was fixed in 7.9.1.

---

<div class="post-metadata">

### Author: ![erigaut](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erigaut/32/75479_2.png) [@erigaut](https://discuss.elastic.co/u/erigaut)
#### Post date: [September 13, 2020, 9:27am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/10 "2020-09-13T09:27:48Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> Which exact version are you on? I recall reading something about a memory leak in 7.9.0 that I believe was fixed in 7.9.1.

Hi, do you have any sources to communicate on this memory leak problem that you mention?

---

<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 13, 2020, 9:43am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/11 "2020-09-13T09:43:25Z")

</div>

> <https://github.com/elastic/elasticsearch/issues/61512>
>
> Lucene 8.6.0 and 8.6.1 contain a slow memory leak which is fixed by LUCENE-9478 in 8.6.2. The only affected Elasticsearch version...

---

<div class="post-metadata">

### Author: ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)
#### Post date: [September 15, 2020, 3:58am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/12 "2020-09-15T03:58:00Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> 7.9.0

Hi,  
I was on 7.9.0, and I just upgraded it to 7.9.1. I will check the status and let you know.  
Thank you for your help.

---

<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 13, 2020, 3:58am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/247637/13 "2020-10-13T03:58:15Z")

</div>

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