# Help reindexing one domain to another

**URL:** <https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603>\
**Category:** Elasticsearch\
**Tags:** reindex\
**Created:** [August 16, 2021, 8:42pm UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603 "2021-08-16T20:42:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ViniciusSPaiva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viniciusspaiva/32/67297_2.png) [@ViniciusSPaiva](https://discuss.elastic.co/u/ViniciusSPaiva)\
**Post date:** [August 16, 2021, 8:42pm UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603/1 "2021-08-16T20:42:49Z")

</div>

Hello,

I am trying to reindex one domain that has almost 10 million documents to another. The reason I am doing that is that I made a change in the analyzer, to split the dots, ignore leading zeroes and so forth.

I'm getting beaten HARD by the \_reindex API. As I write that, I am executing the fourth tentative so far. The problem is that I keep getting this content\_too\_long\_exception and keep decreasing the batch size.

The command I am running is:

> /\_reindex?pretty=true&scroll=10h&wait\_for\_completion=false  
> {  
> "source": {  
> "remote": {  
> "host": "xxxxxxxx",  
> "socket\_timeout": "60m"  
> },  
> "index": "fulltext",  
> "size": 10  
> },  
> "dest": {  
> "index": "fulltext"  
> }  
> }

- I started running with the batch size of 1000, then 500, then 100. Now I got angry and tried 10, but I think every time I do that the total time increases because of the overhead.
- When the task fails isn't there a way to continue from where it stopped? I don't have a date field in my index.
- I don't know what the scroll parameter does
- I keep controlling the status with the GET /\_tasks API. But right now is apparently stuck. This is so slow, I am getting desperate.

Any help would be immensely appreciated

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 16, 2021, 10:02pm UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603/2 "2021-08-16T22:02:56Z")

</div>

It'd be helpful if you could please show the entire error response you are getting.

---

<div class="post-metadata">

**Author:** ![ViniciusSPaiva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viniciusspaiva/32/67297_2.png) [@ViniciusSPaiva](https://discuss.elastic.co/u/ViniciusSPaiva)\
**Post date:** [August 17, 2021, 2:37am UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603/3 "2021-08-17T02:37:07Z")

</div>

> "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 [111951605] for the configured buffer limit [104857600]"  
> }  
> }

---

<div class="post-metadata">

**Author:** ![ViniciusSPaiva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viniciusspaiva/32/67297_2.png) [@ViniciusSPaiva](https://discuss.elastic.co/u/ViniciusSPaiva)\
**Post date:** [August 17, 2021, 11:39am UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603/4 "2021-08-17T11:39:38Z")

</div>

UPDATE:

After trying to reindex four or five times, it got extremely slow, like it is being throttled (I didn't use throttle configuration).

I don't have any clue why, so now I deleting my "destination" domain and creating another.

---

<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:** [September 14, 2021, 11:39am UTC](https://discuss.elastic.co/t/help-reindexing-one-domain-to-another/281603/5 "2021-09-14T11:39:50Z")

</div>

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