Briefly, this error occurs when there’s an attempt to stop the Elasticsearch Watcher service, but it’s not in a state that allows it to be stopped. This could be because it’s already stopped, or it’s in the process of stopping. To resolve this, you can check the current state of the Watcher service. If it’s already stopped, no action is needed. If it’s in the process of stopping, wait for it to complete. If it’s active, try stopping it again. If the problem persists, consider restarting the Elasticsearch service.
This guide will help you check for common problems that cause the log ” watcher has not been stopped. not currently in a stopping state; current state [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “watcher has not been stopped. not currently in a stopping state; current state [{}]” classname is WatcherLifeCycleService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// only transition from stopping -> stopped (which may not be the case if restarted quickly)
boolean stopped = state.compareAndSet(WatcherState.STOPPING; WatcherState.STOPPED);
if (stopped) {
logger.info("watcher has stopped");
} else {
logger.info("watcher has not been stopped. not currently in a stopping state; current state [{}]"; state.get());
}
});
}
}
[ratemypost]
