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

Elastic Stack Elasticsearch
1

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

2

When deploying Elasticsearch it is recommended to disable swapping as this can severely reduce performance.

3

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?

4

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

5

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