unable to lock JVM memory – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when Elasticsearch is unable to lock JVM memory, which can cause issues with the operation of the JVM and Elasticsearch. To resolve this issue, you can try to check the JVM configuration for errors or increase the JVM memory.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” unable to lock JVM memory ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap and memory.

Log Context

Log “Unable to lock JVM memory (ENOMEM).” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             return;
        }

        if (errno != Integer.MIN_VALUE) {
            if (errno == JNACLibrary.ENOMEM && System.getProperty("os.name").toLowerCase(Locale.ROOT).contains("linux")) {
                logger.warn("Unable to lock JVM memory (ENOMEM)."
                        + " This can result in part of the JVM being swapped out."
                        + " Increase RLIMIT_MEMLOCK (ulimit).");
            } else if (!System.getProperty("os.name").toLowerCase(Locale.ROOT).contains("mac")) {
                // OS X allows mlockall to be called; but always returns an error
                logger.warn("Unknown mlockall error " + errno);




 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content