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 OpenSearch is unable to locate the Java Virtual Machine (JVM) in the specified path. It then defaults to using the bundled JDK. This could be due to incorrect JAVA_HOME environment variable or the JVM is not installed. To resolve this, ensure that the JAVA_HOME environment variable is correctly set to the path where your JVM is installed. Alternatively, you can install a JVM if it’s not already installed. Also, ensure that the user running OpenSearch has the necessary permissions to access the JVM directory.
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 ” JVM home [{}]; using bundled JDK [{}]”; System.getProperty(“java.home ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: node.
Log Context
Log “JVM home [{}]; using bundled JDK [{}]”; System.getProperty(“java.home” classname is Node.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
Constants.JVM_NAME;
Constants.JAVA_VERSION;
Constants.JVM_VERSION
);
if (jvmInfo.getBundledJdk()) {
logger.info("JVM home [{}]; using bundled JDK [{}]"; System.getProperty("java.home"); jvmInfo.getUsingBundledJdk());
} else {
logger.info("JVM home [{}]"; System.getProperty("java.home"));
deprecationLogger.deprecate(
"no-jdk";
"no-jdk distributions that do not bundle a JDK are deprecated and will be removed in a future release"
