# Java.exe consuming lot of memory and eventually Elasticsearch searches start failing

**URL:** <https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960>\
**Category:** Elasticsearch\
**Created:** [May 22, 2024, 6:15am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960 "2024-05-22T06:15:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kalidastate](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kalidastate/32/129050_2.png) [@Kalidastate](https://discuss.elastic.co/u/Kalidastate)\
**Post date:** [May 22, 2024, 6:15am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960/1 "2024-05-22T06:15:28Z")

</div>

It has observed in the production environment. When a search is fired, memory consumption of Java.exe increases and it does not reduce even after the search is finished. Eventually the memory consumption reaches to above 95% and searches starts failing.

Environment details:  
How to address this issue?

OS: Windows Server 2016  
RAM: 48 GB  
Paging Configuration: 74 GB on disk  
JVM Heap Size: 8 GB

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 22, 2024, 6:33am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960/2 "2024-05-22T06:33:46Z")

</div>

> [@Kalidastate](#):
>
> Paging Configuration: 74 GB on disk

When deploying Elasticsearch [it is recommended to disable swapping](https://www.elastic.co/guide/en/elasticsearch/reference/8.13/setup-configuration-memory.html) as this can severely reduce performance.

---

<div class="post-metadata">

**Author:** ![Kalidastate](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kalidastate/32/129050_2.png) [@Kalidastate](https://discuss.elastic.co/u/Kalidastate)\
**Post date:** [May 22, 2024, 9:57am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960/3 "2024-05-22T09:57:29Z")

</div>

Thanks @Christian_Dahlqvist for the response.  
I checked the provided link. We are already using bootstrap.memory\_lock: true.  
Regarding the recommendation on disabling the paging/swapping.  
It is not practical to disable the paging/swapping in the production environment.  
Is there any recommendation on minimum paging/swapping memory?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 22, 2024, 9:58am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960/4 "2024-05-22T09:58:30Z")

</div>

> [@Kalidastate](#):
>
> Is there any recommendation on minimum paging/swapping memory?

No. As you can see in the docs the recommendation is to disable it.

---

<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:** [June 19, 2024, 9:59am UTC](https://discuss.elastic.co/t/java-exe-consuming-lot-of-memory-and-eventually-elasticsearch-searches-start-failing/359960/5 "2024-06-19T09:59:12Z")

</div>

Closed on June 19, 2024, 9:59am UTC

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