# Timeout at scroll

**URL:** <https://discuss.elastic.co/t/timeout-at-scroll/241373>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [July 16, 2020, 12:12am UTC](https://discuss.elastic.co/t/timeout-at-scroll/241373 "2020-07-16T00:12:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kinlee](https://avatars.discourse-cdn.com/v4/letter/k/838e76/32.png) [@kinlee](https://discuss.elastic.co/u/kinlee)\
**Post date:** [July 16, 2020, 12:12am UTC](https://discuss.elastic.co/t/timeout-at-scroll/241373/1 "2020-07-16T00:12:48Z")

</div>

I am trying to benchmark on a 3 node cluster using rally. A node is of 7G RAM and 2core. Everything works perfectly until the "running scroll" kicks in. Once the scroll job starts i get error

GET [https://40.77.60.174:9200/pmc/\_search?request\_cache=true](https://40.77.60.174:9200/pmc/_search?request_cache=true) [status:503 request:0.044s]

---

<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:** [August 13, 2020, 12:12am UTC](https://discuss.elastic.co/t/timeout-at-scroll/241373/2 "2020-08-13T00:12:57Z")

</div>

Closed on August 13, 2020, 12:12am UTC

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