# Huge start value brought down the whole cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [May 13, 2016, 6:05am UTC](https://discuss.elastic.co/t/huge-start-value-brought-down-the-whole-cluster/49961 "2016-05-13T06:05:33Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Rural\_Hunter](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@Rural\_Hunter](https://discuss.elastic.co/u/Rural_Hunter)\ **Post date:** [May 13, 2016, 6:05am UTC](https://discuss.elastic.co/t/huge-start-value-brought-down-the-whole-cluster/49961/1 "2016-05-13T06:05:33Z")
Hi, We are running es cluster version 1.5.2. We have several billions of documents in one index. The cluster performance well in normal condition. But we found if we query the index with normal limit but a huge start value eg. several millions or several billions, the memory usage of every node in the cluster soars and then all nodes went into full gc one by one and the whole cluster went down. Is this a expected behavior? How can we avoid that? ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [May 13, 2016, 12:29pm UTC](https://discuss.elastic.co/t/huge-start-value-brought-down-the-whole-cluster/49961/2 "2016-05-13T12:29:26Z")
Don't have a huge start value. In versions like 2.x and onwards by default the query fails when the value in \>10000. Use scroll for scrolling across many results. ---
**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, 10:51pm UTC](https://discuss.elastic.co/t/huge-start-value-brought-down-the-whole-cluster/49961/3 "2017-07-05T22:51:48Z")