# Circuit Breaker Exception - version 5.2.0

**URL:** https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799
**Category:** Elasticsearch
**Created:** [July 28, 2021, 5:31am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799 "2021-07-28T05:31:33Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)
#### Post date: [July 28, 2021, 5:31am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/1 "2021-07-28T05:31:33Z")

</div>

Hi,

Client node is unresponsive and getting error as below

```auto
"org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [<http_request>] would be larger than limit of [24003005644/22.3gb]"
        at org.elasticsearch.indices.breaker.HierarchyCircuitBreakerService.checkParentLimit(HierarchyCircuitBreakerService.java:211) ~[elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.common.breaker.ChildMemoryCircuitBreaker.addEstimateBytesAndMaybeBreak(ChildMemoryCircuitBreaker.java:128) ~[elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.http.HttpServer.dispatchRequest(HttpServer.java:109) [elasticsearch-5.2.0.jar:5.2.0]

```

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 28, 2021, 7:03am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/2 "2021-07-28T07:03:11Z")

</div>

Upgrade. Upgrade. Upgrade.

We fixed so many things since 5.2.

The current version is 7.13.4.

---

<div class="post-metadata">

### Author: ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)
#### Post date: [July 28, 2021, 7:09am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/3 "2021-07-28T07:09:58Z")

</div>

Sure, @dadoonet. Can you please share details about above error.

Thanks

---

<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: [July 28, 2021, 7:38am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/4 "2021-07-28T07:38:18Z")

</div>

5.X has been [EOL](https://www.elastic.co/support/eol) for quiet some time. Please update as a matter of urgency.

This means you are requesting more data than the heap can handle. So either alter your query, increase your heap, or upgrade.

---

<div class="post-metadata">

### Author: ![pfnathan](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@pfnathan](https://discuss.elastic.co/u/pfnathan)
#### Post date: [July 29, 2021, 7:14am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/5 "2021-07-29T07:14:58Z")

</div>

Simple answer is your cluster is out of RAM. Try reducing the amount of indices you have, that might free up enough RAM on the heap to fix this issue.

---

<div class="post-metadata">

### Author: ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)
#### Post date: [July 30, 2021, 12:26am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/6 "2021-07-30T00:26:18Z")

</div>

Thank you

---

<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: [August 27, 2021, 12:26am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-version-5-2-0/279799/7 "2021-08-27T00:26:43Z")

</div>

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