# Scroll on different nodes

**URL:** <https://discuss.elastic.co/t/scroll-on-different-nodes/42089>\
**Category:** Elasticsearch\
**Created:** [February 18, 2016, 1:43am UTC](https://discuss.elastic.co/t/scroll-on-different-nodes/42089 "2016-02-18T01:43:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Borut\_Svara](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@Borut\_Svara](https://discuss.elastic.co/u/Borut_Svara)\
**Post date:** [February 18, 2016, 1:43am UTC](https://discuss.elastic.co/t/scroll-on-different-nodes/42089/1 "2016-02-18T01:43:15Z")

</div>

Hi,

I'm developing now, but i still waiting for hardware to test a proper ES cluster (so I can not test this) but I would prefere to develope in the right way.

I will have few REST servlets serving results queried to a elasticsearch backend. Now, as REST based, user consequent requests may reach different servlets, that may be connected to different ES nodes.

If i start a scroll (giving the scroll\_id to the user) will he be able to get results even if he access other nodes of the cluster or is a scrolling action linked to a specific node and therefore only same-node requests will work?

More:  
My scenario is where the user start scrolling the page and keeps downloading results from the initial query. From what I can think a scroll action would improve the ES performances as query was performed once, but in this scenario is really better over from and size?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 18, 2016, 2:35am UTC](https://discuss.elastic.co/t/scroll-on-different-nodes/42089/2 "2016-02-18T02:35:44Z")

</div>

> [@Borut\_Svara](#):
>
> If i start a scroll (giving the scroll\_id to the user) will he be able to get results even if he access other nodes of the cluster or is a scrolling action linked to a specific node and therefore only same-node requests will work?

It's not stored on the node, so you can connect to any in the cluster.

---

<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:15pm UTC](https://discuss.elastic.co/t/scroll-on-different-nodes/42089/3 "2017-07-05T23:15:29Z")

</div>


