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 OpenSearch operation.
Briefly, this error occurs when the Java Virtual Machine (JVM) memory is being swapped to disk due to insufficient physical memory. This can severely degrade OpenSearch performance. To resolve this, you can increase the physical memory of your system or reduce the JVM heap size. Alternatively, you can disable swapping by setting the “bootstrap.memory_lock” to true in the OpenSearch configuration file. However, this should be done carefully as it can lead to system instability if not enough memory is available for other processes.
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 OpenSearch 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 OpenSearch 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);
