Log Unable to lock JVM memory. Failed to set working set size. Error code – How To Solve Related Issues



Log Unable to lock JVM memory. Failed to set working set size. Error code – How To Solve Related Issues

Opster Team

Jan-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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Unable to lock JVM memory. Failed to set working set size. Error code” 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, memory.


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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”Unable to lock JVM memory. Failed to set working set size. Error code {}” classname is JNANatives.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // By default; Windows limits the number of pages that can be locked.
            // Thus; we need to first increase the working set size of the JVM by
            // the amount of memory we wish to lock; plus a small overhead (1MB).
            SizeT size = new SizeT(JvmInfo.jvmInfo().getMem().getHeapInit().getBytes() + (1024 * 1024));
            if (!kernel.SetProcessWorkingSetSize(process; size; size)) {
                logger.warn("Unable to lock JVM memory. Failed to set working set size. Error code {}"; Native.getLastError());
            } else {
                JNAKernel32Library.MemoryBasicInformation memInfo = new JNAKernel32Library.MemoryBasicInformation();
                long address = 0;
                while (kernel.VirtualQueryEx(process; new Pointer(address); memInfo; memInfo.size()) != 0) {
                    boolean lockable = memInfo.State.longValue() == JNAKernel32Library.MEM_COMMIT




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Unable to lock JVM Memory: error=12, reason=Cannot allocate memory – Elasticsearch 6.2.4 -views 5.38 K ,score 5

How to change Elasticsearch max memory size -views   121.67 K,score 93

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now