# Sorted scroll on large result set (2.4)

**URL:** <https://discuss.elastic.co/t/sorted-scroll-on-large-result-set-2-4/126583>\
**Category:** Elasticsearch\
**Created:** [April 3, 2018, 1:50pm UTC](https://discuss.elastic.co/t/sorted-scroll-on-large-result-set-2-4/126583 "2018-04-03T13:50:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fnork](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fnork](https://discuss.elastic.co/u/fnork)\
**Post date:** [April 3, 2018, 1:50pm UTC](https://discuss.elastic.co/t/sorted-scroll-on-large-result-set-2-4/126583/1 "2018-04-03T13:50:02Z")

</div>

I'm investigating a cluster (running 2.4) where sorted scroll queries fails in the middle of retrieving the result set.

The result sets are very large (millions of docs). My impression is that large sorted scrolls are very cpu intensive. Could the cpu activity lead to the cluster node becoming unresponsive resulting in the Java client transport connection dropping the connection?

Some of the indexes also have very large mappings (10000+ fields). Can this have an impact on scrolls with sort?

Have anyone else done large sorted scrolls with or without success?

Kind regards

André

---

<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 1, 2018, 2:00pm UTC](https://discuss.elastic.co/t/sorted-scroll-on-large-result-set-2-4/126583/2 "2018-05-01T14:00:25Z")

</div>

Closed on May 1, 2018, 2:00pm UTC

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