Unable to lock JVM Memory: error= – How to solve related issues

Average Read Time

2 Mins

Unable to lock JVM Memory: error= – 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 can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

             // this will have already been logged by CLibrary; no need to repeat it
            return;
        }

        // mlockall failed for some reason
        logger.warn("Unable to lock JVM Memory: error=" + errno + ";reason=" + 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: " + rlimitToString(softLimit) + "; hard limit: " + rlimitToString(hardLimit));
                if (Constants.LINUX) {




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content