Elasticsearch killed by Linux OOM Killer
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- Linux Out of Memory Killer stops the Elasticsearch Java process
- OOM Killer is killing ES
Environment
Resolution
- Set a limit on how much memory Elasticsearch can use outside the heap
1. Elasticsearch can consume memory outside of the JVM heap
2. Direct memory is a major consumer of off-heap memory
3. The JVM itself requires some amount of memory
Elastic recommends setting the following parameter on each node to half of the available heap memory size:
-XX:MaxDirectMemorySize
Note:
- For Elasticsearch 7.2 and above, this parameter is automatically set to half the heap size
- For lower versions, it is unset by default
Did this article resolve your issue ?
