# Number of scroll contexts created by reindex

**URL:** <https://discuss.elastic.co/t/number-of-scroll-contexts-created-by-reindex/230051>\
**Category:** Elasticsearch\
**Created:** [April 28, 2020, 12:20am UTC](https://discuss.elastic.co/t/number-of-scroll-contexts-created-by-reindex/230051 "2020-04-28T00:20:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bobbyi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bobbyi/32/27949_2.png) [@bobbyi](https://discuss.elastic.co/u/bobbyi)\
**Post date:** [April 28, 2020, 12:20am UTC](https://discuss.elastic.co/t/number-of-scroll-contexts-created-by-reindex/230051/1 "2020-04-28T00:20:39Z")

</div>

I am performing a reindex operation from one index to another within the same cluster running ES 7.5.1. I am using slices=32 and I thought this meant that 32 scroll contexts would be created and used in parallel to pull data from the source to the destination.

However, when running the reindex, I am seeing hundreds of scroll contexts being created. I have confirmed they are coming from the single reindex operation and not some other activity happening at the same time (or left over from earlier). Is this expected? What determines how many scroll contexts a reindex API call will use?

Specifically, I am calling the API like this:

```
curl -X POST <my_cluster>:9200/_reindex?slices=32 -H 'Content-Type: application/json' -d '
{
    "dest": {
        "index": <src_index>
    },
    "source": {
        "index": <dest_index>,
        "size": 5000,
        "query": <my_query>
    }
}
'
```

---

<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:** [May 26, 2020, 12:20am UTC](https://discuss.elastic.co/t/number-of-scroll-contexts-created-by-reindex/230051/2 "2020-05-26T00:20:39Z")

</div>

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