This can result in part of the JVM being swapped out – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the Elasticsearch Java Virtual Machine (JVM) is swapped out due to insufficient memory. This can degrade the performance of Elasticsearch. To resolve this issue, you can disable swapping by setting bootstrap.memory_lock to true in the Elasticsearch configuration file. Alternatively, you can increase the system’s RAM or adjust the JVM heap size to ensure it has enough memory to operate efficiently. Also, ensure that the Elasticsearch process has the necessary permissions to lock the memory.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” This can result in part of the JVM being swapped out. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap.

Log Context

Log “This can result in part of the JVM being swapped out.” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            return;
        }

        // mlockall failed for some reason
        logger.warn("Unable to lock JVM Memory: error={}; reason={}"; errno; errMsg);
        logger.warn("This can result in part of the JVM being swapped out.");
        if (errno == JNACLibrary.ENOMEM) {
            if (rlimitSuccess) {
                logger.warn(
                    "Increase RLIMIT_MEMLOCK; soft limit: {}; hard limit: {}";
                    rlimitToString(softLimit);

 

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?