Log Unable to lock JVM Memory: error= – How To Solve Related Issues


Log 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 try running the 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: bootstrap.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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) {




 

Optimize Elasticsearch Performance

Try The Tool