# Circuit Breaker \[parent\] Data too large, data for \[\\] **URL:** \ **Category:** Elasticsearch\ **Created:** [June 28, 2017, 5:36am UTC](https://discuss.elastic.co/t/circuit-breaker-parent-data-too-large-data-for-http-request/91044 "2017-06-28T05:36:06Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ori.rubinfeld](https://avatars.discourse-cdn.com/v4/letter/o/7c8e57/32.png) [@ori.rubinfeld](https://discuss.elastic.co/u/ori.rubinfeld)\ **Post date:** [June 28, 2017, 5:36am UTC](https://discuss.elastic.co/t/circuit-breaker-parent-data-too-large-data-for-http-request/91044/1 "2017-06-28T05:36:06Z")
Hi, We are running Elasticsearch version 5.0 as production. Using the Ingest Node to parse the logs data. Logs are being sent by Filebeat Version 5.0 There are more than 25 different logs types being sent, each log with a different structure. Cluster is composed from: 2 Master + Ingest Nodes 1 Master + Data node 2 Data Nodes After the cluster is running for some time, both of the Ingest nodes are failing with the Message: {"error":{"root\_cause":[{"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for [\] would be larger than limit of [2982071500/2.7gb]","bytes\_wanted":2982082632,"bytes\_limit":2982071500}],"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for [\] would be larger than limit of [2982071500/2.7gb]","bytes\_wanted":2982082632,"bytes\_limit":2982071500},"status":503} Only a Restart to each of those two nodes will solve it. We are encountering it on a Daily basis. I found the followings: [https://discuss.elastic.co/t/circuit-breaking-exception-parent-data-too-large-data-for-http-request-would-be-larger-than-limit-of-2994274304-2-7gb/77353](https://discuss.elastic.co/t/circuit-breaking-exception-parent-data-too-large-data-for-http-request-would-be-larger-than-limit-of-2994274304-2-7gb/77353) > [@Request Circuit Breaker keeps tripping; how is the estimate calculated?](https://discuss.elastic.co/t/request-circuit-breaker-keeps-tripping-how-is-the-estimate-calculated/77185): > > We have an ES cluster that is having issues with the circuit breaker. Initially, it seemed tied to our field data. As an experiment, we migrated our index over to a copy with field data turned off. Now, we are still tripping a circuit breaker on transport\_request. The cluster has: 11 data nodes, 1 index, 60 total shards (20 shards: 1 primary, 2 replicas each), about 50 million documents. Individual Cluster node Memory: 10 GB allocated for ES JVM heap (32GB total memory per machine) Request Ci… Which states that there is a Bug which was solved on version 5.2.2 Before going to Upgrade, I would like to know, if there are other options, as: Our Elasticsearch output config for each Filebeat is with Bulk Size of 10,000 If we will reduce the Bulk Size, can it Solve the issue, is there a correlation between that parameter and the issue ? Which other or additional config parameters can help to workaround it ? Thanks, Ori ---
**Author:** ![ori.rubinfeld](https://avatars.discourse-cdn.com/v4/letter/o/7c8e57/32.png) [@ori.rubinfeld](https://discuss.elastic.co/u/ori.rubinfeld)\ **Post date:** [July 10, 2017, 6:54am UTC](https://discuss.elastic.co/t/circuit-breaker-parent-data-too-large-data-for-http-request/91044/2 "2017-07-10T06:54:33Z")
Anyone ? Ori ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 7, 2017, 6:55am UTC](https://discuss.elastic.co/t/circuit-breaker-parent-data-too-large-data-for-http-request/91044/3 "2017-08-07T06:55:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.