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 successfully starts a node or a shard. It’s not an error message but an informational message indicating that a node or shard has been started successfully. If you see this message frequently, it might indicate that your nodes or shards are frequently going down and coming back up. To resolve this, you should investigate the root cause of the instability. This could be due to hardware issues, network problems, or configuration errors. Ensure your system has adequate resources and your OpenSearch configuration is correct.
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 ” started ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: node.
Log Context
Log “started” classname is Node.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
writePortsFile("transport"; transport.boundAddress());
HttpServerTransport http = injector.getInstance(HttpServerTransport.class);
writePortsFile("http"; http.boundAddress());
}
logger.info("started");
pluginsService.filterPlugins(ClusterPlugin.class).forEach(plugin -> plugin.onNodeStarted(clusterService.localNode()));
return this;
}
