# Error 29 Too Many Requests and circuit breaking exception

**URL:** <https://discuss.elastic.co/t/error-29-too-many-requests-and-circuit-breaking-exception/216732>\
**Category:** Elasticsearch\
**Created:** [January 27, 2020, 10:30pm UTC](https://discuss.elastic.co/t/error-29-too-many-requests-and-circuit-breaking-exception/216732 "2020-01-27T22:30:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbalaguero](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jbalaguero](https://discuss.elastic.co/u/jbalaguero)\
**Post date:** [January 27, 2020, 10:30pm UTC](https://discuss.elastic.co/t/error-29-too-many-requests-and-circuit-breaking-exception/216732/1 "2020-01-27T22:30:06Z")

</div>

Hi ES team,

We are getting this error from ES 7.4.1, querying an empty index (every 2s) on a server with no load (it's still in test mode so it's not receiving any request). We tried to increase the heap size from 2g to 4g, but no success.

It's a one-node installation with CPU 32c RAM 128GB, HEAP SIZE 4GB (Linux Centos7, Zing JVM 1.8.0-zing\_19.12.100.0)

The piece of code that returns this error is:

```
SearchRequest sr = new SearchRequest(this.pi.getIndexName()).source(new SearchSourceBuilder().query(QueryBuilders.matchAllQuery()).fetchSource(false).version(false));
SearchHit[] searchHits = cluster.getRestClient().search(sr, cluster.getRequestOptions()).getHits().getHits();

```

The error is:

ElasticsearchStatusException[Elasticsearch exception [type=circuit\_breaking\_exception, reason=[parent] Data too large, data for [\<http\_request\>] would be [3110076554/2.8gb], which is larger than the limit of [3026295193/2.8gb], real usage: [3110076416/2.8gb], new bytes reserved: [138/138b], usages [request=0/0b, fielddata=0/0b, in\_flight\_requests=138/138b, accounting=0/0b]]]  
at org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:177)  
at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1727)  
at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:1704)  
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1467)  
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1424)  
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1394)  
at org.elasticsearch.client.RestHighLevelClient.search(RestHighLevelClient.java:930)  
at com.ventusproxy.proxy.cluster.elasticsearch.CleanPercolator.run(CleanPercolator.java:49)  
at java.lang.Thread.run(Thread.java:748)  
Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [[http://127.0.0.1:9200](http://127.0.0.1:9200)], URI [/pc\_102/\_search?typed\_keys=true&ignore\_unavailable=false&expand\_wildcards=open&allow\_no\_indices=true&ignore\_throttled=true&search\_type=query\_then\_fetch&batched\_reduce\_size=512&ccs\_minimize\_roundtrips=true], status line [HTTP/1.1 429 Too Many Requests] {"error":{"root\_cause":[{"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for [\<http\_request\>] would be [3110076554/2.8gb], which is larger than the limit of [3026295193/2.8gb], real usage: [3110076416/2.8gb], new bytes reserved: [138/138b], usages [request=0/0b, fielddata=0/0b, in\_flight\_requests=138/138b, accounting=0/0b]","bytes\_wanted":3110076554,"bytes\_limit":3026295193,"durability":"TRANSIENT"}],"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for [\<http\_request\>] would be [3110076554/2.8gb], which is larger than the limit of [3026295193/2.8gb], real usage: [3110076416/2.8gb], new bytes reserved: [138/138b], usages [request=0/0b, fielddata=0/0b, in\_flight\_requests=138/138b, accounting=0/0b]","bytes\_wanted":3110076554,"bytes\_limit":3026295193,"durability":"TRANSIENT"},"status":429}  
at org.elasticsearch.client.RestClient.convertResponse(RestClient.java:253)  
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:231)  
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:205)  
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1454)  
... 5 more  
.

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:** [February 24, 2020, 10:44pm UTC](https://discuss.elastic.co/t/error-29-too-many-requests-and-circuit-breaking-exception/216732/2 "2020-02-24T22:44:49Z")

</div>

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

---

<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:** [March 4, 2020, 11:50am UTC](https://discuss.elastic.co/t/error-29-too-many-requests-and-circuit-breaking-exception/216732/3 "2020-03-04T11:50:06Z")

</div>

Hi @jbalaguero,

I notice that you use zing JVM. You might be interested in this post here:

> [@CircuitBreakingException: \[parent\] Data too large IN ES 7.x](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801/19):
>
> Just to update, we solved the issue of Azul Zing JDK with -XX:GPGCTargetPeakHeapOccupancyPercent=95 Our jvm.conf right now: -Dio.netty.noKeySetOptimization=true -Dio.netty.noUnsafe=true -Dio.netty.recycler.maxCapacityPerThread=0 -Djava.awt.headless=true -Djna.nosys=true -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -XX:+AlwaysPreTouch -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -XX:GPGCTargetPeakHeapOccupancyPercent=95 -Xloggc:/var/log/elasticsearch/dba/gc.log …
