# Elasticsearch-rest-client-5.6.1.jar org.apache.http.ContentTooLongException: entity content is too long \[217056451\] for the configured buffer limit \[104857600\]

**URL:** <https://discuss.elastic.co/t/elasticsearch-rest-client-5-6-1-jar-org-apache-http-contenttoolongexception-entity-content-is-too-long-217056451-for-the-configured-buffer-limit-104857600/101387>\
**Category:** Elasticsearch\
**Created:** [September 21, 2017, 7:48pm UTC](https://discuss.elastic.co/t/elasticsearch-rest-client-5-6-1-jar-org-apache-http-contenttoolongexception-entity-content-is-too-long-217056451-for-the-configured-buffer-limit-104857600/101387 "2017-09-21T19:48:38Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 22, 2017, 5:52pm UTC](https://discuss.elastic.co/t/elasticsearch-rest-client-5-6-1-jar-org-apache-http-contenttoolongexception-entity-content-is-too-long-217056451-for-the-configured-buffer-limit-104857600/101387/6 "2017-09-22T17:52:31Z")

</div>

I'd not do that.

But if you really want to overload your data nodes and your client, up to you.

Did you read the workaround that Tanguy mentioned in the issue I linked to?

Specifically that class:

> <https://github.com/elastic/elasticsearch/blob/706067211ae880bbe4669286ee976552e8a60446/client/rest/src/main/java/org/elasticsearch/client/HttpAsyncResponseConsumerFactory.java#L49-L64>

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-rest-client-5-6-1-jar-org-apache-http-contenttoolongexception-entity-content-is-too-long-217056451-for-the-configured-buffer-limit-104857600/101387)._