# Reindexing a document of size \> 100mb

**URL:** <https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765>\
**Category:** Elasticsearch\
**Created:** [October 16, 2019, 7:40am UTC](https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765 "2019-10-16T07:40:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![daso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daso/32/56016_2.png) [@daso](https://discuss.elastic.co/u/daso)\
**Post date:** [October 16, 2019, 7:40am UTC](https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765/1 "2019-10-16T07:40:58Z")

</div>

Hi,  
I am trying to do a remote reindex a document which is of size \>100mb but it is failing with the below exception

error={type=illegal\_argument\_exception, reason=Remote responded with a chunk that was too large. Use a smaller batch size., caused\_by={type=content\_too\_long\_exception, reason=entity content is too long [185463385] for the configured buffer limit [104857600]}}}

I even tried increasing the **http.max\_content\_length** to 500MB but still, it is failing with the same exception. Is there any way to increase this limit or is there any workaround to reindex such documents.

---

<div class="post-metadata">

**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\
**Post date:** [October 16, 2019, 5:56pm UTC](https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765/2 "2019-10-16T17:56:59Z")

</div>

Let's start by verifying that it is applied correctly: Can you post the relevant output of the query `GET /_cluster/settings?include_defaults=true` please? This isn't a dynamic setting and must be set in the YML configuration on all hosts.

BUT the bigger question is why you need this. A single document with more than a 100MB sounds like something is very wrong. I'd strongly suggest to restructure your data instead of changing the setting, which is generally a good protection for your cluster.

---

<div class="post-metadata">

**Author:** ![daso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daso/32/56016_2.png) [@daso](https://discuss.elastic.co/u/daso)\
**Post date:** [October 17, 2019, 7:10am UTC](https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765/3 "2019-10-17T07:10:30Z")

</div>

Hi xeraa,  
I have attached the response of the settings call [here](https://github.com/dhivakar-asokan/elastic/blob/master/settings.json).

I understand that documents of size 100 MB is not advisable. But when we have docs like 10-20MB, we are forced to use the batch size less than 5 during bulk reindexing. With this batch size, reindexing a huge index takes more time. So we wanted to increase this 100MB limit to a reasonably bigger number. Please advise

---

<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:** [November 14, 2019, 7:10am UTC](https://discuss.elastic.co/t/reindexing-a-document-of-size-100mb/203765/4 "2019-11-14T07:10:34Z")

</div>

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