# I got issue about "Data too large"

**URL:** <https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087>\
**Category:** Elasticsearch\
**Created:** [June 11, 2019, 4:28am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087 "2019-06-11T04:28:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![thachnv92](https://avatars.discourse-cdn.com/v4/letter/t/a6a055/32.png) [@thachnv92](https://discuss.elastic.co/u/thachnv92)\
**Post date:** [June 11, 2019, 4:28am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087/1 "2019-06-11T04:28:56Z")

</div>

Hello, I installed ELK version 7.1.0.

After I ran all modules, I got messages:

**At Logstash:**  
`[2019-06-11T03:43:27,582][INFO][logstash.outputs.elasticsearch] retrying failed action with response code: 429 ({"type"=>"circuit_breaking_exception", "reason"=>"[parent] Data too large, data for [<transport_request>] would be [1030230716/982.5mb], which is larger than the limit of [986061209/940.3mb], real usage: [1029991544/982.2mb], new bytes reserved: [239172/233.5kb]", "bytes_wanted"=>1030230716, "bytes_limit"=>986061209, "durability"=>"TRANSIENT"}) [INFO][logstash.outputs.elasticsearch] Retrying individual bulk actions that failed or were rejected by the previous bulk request. {:count=>382}`

`[2019-06-11T03:57:49,643][WARN][logstash.outputs.elasticsearch] Marking url as dead. Last error: [LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError] Elasticsearch Unreachable: [https://logstash:xxxxxx@elastic:9200/][Manticore::SocketTimeout] Read timed out {:url=>https://logstash:xxxxxx@elastic:9200/, :error_message=>"Elasticsearch Unreachable: [https://logstash:xxxxxx@elastic:9200/][Manticore::SocketTimeout] Read timed out", :error_class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError"} [2019-06-11T03:57:49,644][ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request to elasticsearch' but Elasticsearch appears to be unreachable or down! {:error_message=>"Elasticsearch Unreachable: [https://logstash:xxxxxx@elastic:9200/][Manticore::SocketTimeout] Read timed out", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError", :will_retry_in_seconds=>2}`

**At Elasticsearch:**  
`{"error":{"root_cause":[{"type":"circuit_breaking_exception","reason":"[parent] Data too large, data for [<http_request>] would be [1018342960/971.1mb], which is larger than the limit of [986061209/940.3mb], real usage: [1018342960/971.1mb], new bytes reserved: [0/0b]","bytes_wanted":1018342960,"bytes_limit":986061209,"durability":"TRANSIENT"}],"type":"circuit_breaking_exception","reason":"[parent] Data too large, data for [<http_request>] would be [1018342960/971.1mb], which is larger than the limit of [986061209/940.3mb], real usage: [1018342960/971.1mb], new bytes reserved: [0/0b]","bytes_wanted":1018342960,"bytes_limit":986061209,"durability":"TRANSIENT"},"status":429}`

**At Kibana:**  
`[circuit_breaking_exception] [parent] Data too large, data for [<http_request>] would be [1004465832/957.9mb], which is larger than the limit of [986061209/940.3mb], real usage: [1004465832/957.9mb], new bytes reserved: [0/0b], with { bytes_wanted=1004465832 & bytes_limit=986061209 & durability="TRANSIENT" }`

I don't understand "circuit\_breaking\_exception".  
Please help me.  
Thanks.

---

<div class="post-metadata">

**Author:** ![pathri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pathri/32/54484_2.png) [@pathri](https://discuss.elastic.co/u/pathri)\
**Post date:** [June 11, 2019, 5:05am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087/2 "2019-06-11T05:05:52Z")

</div>

> [@thachnv92](#):
>
> bytes\_wanted":1018342960,"bytes\_limit":986061209,"durability":"TRANSIENT"}],"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for

have a look once at jvm.properties file and try to increase the size over there to  
-Xms4g  
-Xmx4g

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 11, 2019, 5:15am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087/3 "2019-06-11T05:15:52Z")

</div>

Either increase your heap size or try and reduce the size of your bulk requests.

---

<div class="post-metadata">

**Author:** ![thachnv92](https://avatars.discourse-cdn.com/v4/letter/t/a6a055/32.png) [@thachnv92](https://discuss.elastic.co/u/thachnv92)\
**Post date:** [June 11, 2019, 7:03am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087/4 "2019-06-11T07:03:00Z")

</div>

Yeap, thanks @pathri and @Christian_Dahlqvist.  
I forgot increase heap size.  
I stop half of number logstash and checking logs.

**Increase heap size is way to resolve this problem.**

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:** [July 9, 2019, 7:03am UTC](https://discuss.elastic.co/t/i-got-issue-about-data-too-large/185087/5 "2019-07-09T07:03:16Z")

</div>

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