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 trying to shut down in a controlled manner on a Windows system, but encounters issues. This could be due to processes still running or resources being locked. To resolve this, you can try manually stopping any running OpenSearch processes through the Task Manager. Alternatively, you can use the ‘net stop’ command in the command prompt to stop the OpenSearch service. If the issue persists, consider checking for any locked files or resources that may be preventing the graceful exit and release them.
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 ” running graceful exit on windows ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: bootstrap.
Log Context
Log “running graceful exit on windows” classname is Bootstrap.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
if (ctrlHandler) {
Natives.addConsoleCtrlHandler(new ConsoleCtrlHandler() {
@Override
public boolean handle(int code) {
if (CTRL_CLOSE_EVENT == code) {
logger.info("running graceful exit on windows");
try {
Bootstrap.stop();
} catch (IOException e) {
throw new OpenSearchException("failed to stop node"; e);
}
