# Elasticsearch cluster crash due to circuit breakdown issue

**URL:** <https://discuss.elastic.co/t/elasticsearch-cluster-crash-due-to-circuit-breakdown-issue/232824>\
**Category:** Elasticsearch\
**Created:** [May 15, 2020, 1:01pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-crash-due-to-circuit-breakdown-issue/232824 "2020-05-15T13:01:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Khajan\_Singh\_Bisht](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/khajan_singh_bisht/32/55148_2.png) [@Khajan\_Singh\_Bisht](https://discuss.elastic.co/u/Khajan_Singh_Bisht)\
**Post date:** [May 15, 2020, 1:01pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-crash-due-to-circuit-breakdown-issue/232824/1 "2020-05-15T13:01:02Z")

</div>

Hi,

Currently elasticsearch cluster is getting crashed and showing error related to circuit breakdown.

While hitting kibana url I am getting below screen.

 ![Screenshot from 2020-05-15 18-03-10](https://us1.discourse-cdn.com/elastic/original/3X/a/1/a1a8390874b47cb21c751213f539a800a30e926b.jpeg)

While further debugging I found logs regarding circuit breaker,

```auto
{"statusCode":500,"error":"Internal Server Error","message":"[parent] Data too large, data for [<http_request>] would be [13903957752/12.9gb], which is larger than the limit of [13891534848/12.9gb], real usage: [13903957752/12.9gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=190582/186.1kb, in_flight_requests=776/776b, accounting=133044177/126.8mb]: [circuit_breaking_exception] [parent] Data too large, data for [<http_request>] would be [13903957752/12.9gb], which is larger than the limit of [13891534848/12.9gb], real usage: [13903957752/12.9gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=190582/186.1kb, in_flight_requests=776/776b, accounting=133044177/126.8mb], with { bytes_wanted=13903957752 & bytes_limit=13891534848 & durability=\"PERMANENT\" }"}

```

I tried to increase the parent circuit breaker limit from default 70% to 90% using cluster setting api but still facing same issue. I even tried to increase the heap size from 15Gb to 18Gb but after that also I faced same problem. It is happening from a week frequently.

Version using -  
Java - openjdk version "1.8.0\_252"  
Elasticsearch - 7.5.0  
Logstash - 7.5.0  
File descriptors on each elasticsearch node - 200000

Running three nodes of elasticsearch with one a master node. Two node consist of elasticsearch and logstash on same machine for logstash HA.

Elasticsearch jvm.options file contains with 18G heap size.

```auto
-Xms18g
-Xmx18g
## GC configuration
#-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly

```

Jvm memory, reaches 80% - 90% most of time on all nodes.

- Temporary solution - For now I just restart one of the nodes, and everything goes back to normal. But it happens again anytime. I am facing this issue more than once a day.

Does downgrading/upgrading Elasticsearch will lead to any solution ? Or just need to do changes in jvm.options file will resolve the issue.

Any direction or thoughts would be really helpful.

---

<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:** [June 12, 2020, 1:01pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-crash-due-to-circuit-breakdown-issue/232824/2 "2020-06-12T13:01:07Z")

</div>

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