# Magento 2.4.1 with Elasticsearch 7.10

**URL:** https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585
**Category:** Elasticsearch
**Created:** [December 3, 2020, 8:37pm UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585 "2020-12-03T20:37:50Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![ioannigz](https://avatars.discourse-cdn.com/v4/letter/i/74df32/32.png) [@ioannigz](https://discuss.elastic.co/u/ioannigz)
#### Post date: [December 3, 2020, 8:37pm UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/1 "2020-12-03T20:37:50Z")

</div>

Hi....If anyone has experience with Magento and Elasticsearch please?

We have this strange issue which came up latest days.

We use magento 2.4.1 and elasticsearch 7.10  
Our catalog contains about 600 categories with 20000 skus.  
Everytime we hit a category in front end we get error:

```auto
1 exception(s):
Exception #0 (Elasticsearch\Common\Exceptions\BadRequest400Exception): {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Result window is too large, from + size must be less than or equal to: [10000] but was [11424]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting."}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"magento2_product_3_v16","node":"qNslYqZBRNiOlZuAWbzLGQ","reason":{"type":"illegal_argument_exception","reason":"Result window is too large, from + size must be less than or equal to: [10000] but was [11424]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting."}}],"caused_by":{"type":"illegal_argument_exception","reason":"Result window is too large, from + size must be less than or equal to: [10000] but was [11424]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting.","caused_by":{"type":"illegal_argument_exception","reason":"Result window is too large, from + size must be less than or equal to: [10000] but was [11424]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting."}}},"status":400}

```

We don't have any error in reindex process and everything seems fine in magento.

Any ideas please would much appreciated  
Thanks in advance

---

<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: [December 3, 2020, 9:57pm UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/2 "2020-12-03T21:57:26Z")

</div>

By default Elasticsearch only allows the search endpoint to return 10000, see [Index modules | Elasticsearch Guide [7.10] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/index-modules.html);

> The maximum value of `from + size` for searches to this index. Defaults to `10000` . Search requests take heap memory and time proportional to `from + size` and this limits that memory. See [Scroll](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/paginate-search-results.html#scroll-search-results) or [Search After](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/paginate-search-results.html#search-after) for a more efficient alternative to raising this.

It sounds like you might want to chat to the Magento developers about dealing with \>10K results.

---

<div class="post-metadata">

### Author: ![ioannigz](https://avatars.discourse-cdn.com/v4/letter/i/74df32/32.png) [@ioannigz](https://discuss.elastic.co/u/ioannigz)
#### Post date: [December 4, 2020, 4:29am UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/3 "2020-12-04T04:29:55Z")

</div>

The thing is that this store have these amount of product a lot of years. And this issue came up some days ago

---

<div class="post-metadata">

### Author: ![trotlix](https://avatars.discourse-cdn.com/v4/letter/t/c6cbf5/32.png) [@trotlix](https://discuss.elastic.co/u/trotlix)
#### Post date: [December 29, 2020, 10:28pm UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/4 "2020-12-29T22:28:31Z")

</div>

Hi,  
I was wondering whether you found some solution? I have the same issue....  
Viktor

---

<div class="post-metadata">

### Author: ![ioannigz](https://avatars.discourse-cdn.com/v4/letter/i/74df32/32.png) [@ioannigz](https://discuss.elastic.co/u/ioannigz)
#### Post date: [December 30, 2020, 11:35am UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/5 "2020-12-30T11:35:17Z")

</div>

I didn't yet. Do you use any layered navigation module? It seems that this error comes from amasty layered

---

<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: [January 27, 2021, 11:35am UTC](https://discuss.elastic.co/t/magento-2-4-1-with-elasticsearch-7-10/257585/6 "2021-01-27T11:35:33Z")

</div>

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