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 in the process of shutting down or has received a command to stop its operations. This could be due to a manual shutdown, a system error, or a resource issue. To resolve this, ensure that the shutdown was intentional. If not, check system logs for any errors that may have triggered the shutdown. If it’s a resource issue, consider scaling up your server or optimizing your OpenSearch configurations to use resources more efficiently. Always ensure to have a proper backup and recovery plan in place to prevent data loss.
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 ” stopping … ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: node.
Log Context
Log “stopping …” classname is Node.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
private Node stop() {
if (!lifecycle.moveToStopped()) {
return this;
}
logger.info("stopping ...");
injector.getInstance(ResourceWatcherService.class).close();
injector.getInstance(HttpServerTransport.class).stop();
injector.getInstance(SnapshotsService.class).stop();
