# Circuit breaker exception Elasticsearch

**URL:** <https://discuss.elastic.co/t/circuit-breaker-exception-elasticsearch/197011>\
**Category:** Elasticsearch\
**Created:** [August 27, 2019, 10:29pm UTC](https://discuss.elastic.co/t/circuit-breaker-exception-elasticsearch/197011 "2019-08-27T22:29:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cool\_guy99](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cool_guy99/32/46406_2.png) [@cool\_guy99](https://discuss.elastic.co/u/cool_guy99)\
**Post date:** [August 27, 2019, 10:29pm UTC](https://discuss.elastic.co/t/circuit-breaker-exception-elasticsearch/197011/1 "2019-08-27T22:29:37Z")

</div>

Im seeing the following errors while creating the index

failed shard on node : failed recovery, failure RecoveryFailedException[[index\_1][1]: Recovery failed from {Node\_name}{Node\_name}{Node\_name}{NodeIP}{NodeIP:9300}{rack\_cloud=Cloud1} into {es-data-Node}{Node\_name}{Node\_name}{NodeIP}{NodeIP:9300}{rack\_cloud=Cloud1}]; nested: RemoteTransportException[[Node\_name][NopeIP:9300][internal:index/shard/recovery/start\_recovery]]; nested: CircuitBreakingException[[parent] Data too large, data for [\<transport\_request\>] would be [20412311022/19gb], which is larger than the limit of [20293386240/18.8gb], real usage: [20412250920/19gb], new bytes reserved: [60102/58.6kb]];

This happened a few days ago, but when I tried to check the node stats currently, I do not see any higher parent circuit breaker limit reached in any of my nodes. How can I clear my unassigned shards here?

---

<div class="post-metadata">

**Author:** ![HenningAndersen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/henningandersen/32/48188_2.png) [@HenningAndersen](https://discuss.elastic.co/u/HenningAndersen)\
**Post date:** [August 30, 2019, 11:44am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-elasticsearch/197011/2 "2019-08-30T11:44:52Z")

</div>

Hi @cool_guy99,

the log file looks like it is taken from a 7.0+ system. Are you using G1 GC? If so, setting

```auto
-XX:G1ReservePercent=25
-XX:InitiatingHeapOccupancyPercent=30

```

might help here and I would be very interested in hearing the results.

---

<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:** [September 27, 2019, 11:44am UTC](https://discuss.elastic.co/t/circuit-breaker-exception-elasticsearch/197011/3 "2019-09-27T11:44:59Z")

</div>

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