# Maximum Scroll Context

**URL:** <https://discuss.elastic.co/t/maximum-scroll-context/384754>\
**Category:** Elasticsearch\
**Created:** [January 27, 2026, 10:36am UTC](https://discuss.elastic.co/t/maximum-scroll-context/384754 "2026-01-27T10:36:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [January 27, 2026, 4:59pm UTC](https://discuss.elastic.co/t/maximum-scroll-context/384754/2 "2026-01-27T16:59:27Z")

</div>

Welcome back @Lakshya_Gupta

It might be useful to reference the long previous discussion around your cluster, though I doubt anyone will read all of it (again):

> [@High CPU Usage on a few data nodes / Hotspotting of data](https://discuss.elastic.co/t/high-cpu-usage-on-a-few-data-nodes-hotspotting-of-data/383954/201):
>
> Sure, thanks a lot for the support!

Note I do recognize it's a different question(s() yu are asking today.

"if the data only exists on the 5 nodes, will the scroll instantly close on the remaining"

I'm not an expert on the internals, but I would expect no scroll context to be created on nodes with no matching data, never mind "instantly close"?

btw you can see the counts in output of a GET to

`_nodes/stats/indices/search`

so should not be too hard to validate the behavior

---

_[View the full topic](https://discuss.elastic.co/t/maximum-scroll-context/384754)._
