# Parallel scan/scroll

**URL:** <https://discuss.elastic.co/t/parallel-scan-scroll/35029>\
**Category:** Elasticsearch\
**Created:** [November 19, 2015, 9:12am UTC](https://discuss.elastic.co/t/parallel-scan-scroll/35029 "2015-11-19T09:12:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![liorg2](https://avatars.discourse-cdn.com/v4/letter/l/ed8c4c/32.png) [@liorg2](https://discuss.elastic.co/u/liorg2)\
**Post date:** [November 19, 2015, 9:12am UTC](https://discuss.elastic.co/t/parallel-scan-scroll/35029/1 "2015-11-19T09:12:56Z")

</div>

hello,

is there an option to perform scan&scroll in parallel. (client side)  
sometimes it takes 6 seconds between scroll iterations

the problem i see, is that the scrollid may be changed.

in the server side: is it multithreaded? is there a setting to configure how many threads participating in it?

Lior

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [November 19, 2015, 2:23pm UTC](https://discuss.elastic.co/t/parallel-scan-scroll/35029/2 "2015-11-19T14:23:54Z")

</div>

On the server side, there is one working thread per shard.

As you said, scroll ids can change so if you want to parallelize logic on client-side, you still need to make sure that the call to get the next page is not parallelized.

---

<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 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/parallel-scan-scroll/35029/3 "2017-07-05T23:37:15Z")

</div>