Briefly, this error occurs when Elasticsearch is in the process of shutting down, and as part of this process, it stops the watch service. The watch service is responsible for alerting and monitoring in Elasticsearch. This is a normal part of the shutdown process and not necessarily an error. However, if this happens unexpectedly, it could be due to issues like insufficient resources, configuration errors, or unhandled exceptions. To resolve this, ensure that Elasticsearch has enough resources, check your configurations, and monitor your logs for any exceptions or errors that could cause an unexpected shutdown.
This guide will help you check for common problems that cause the log ” stopping watch service; reason [shutdown initiated] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “stopping watch service; reason [shutdown initiated]” classname is WatcherService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
*
* @param stoppedListener The listener that will set Watcher state to: {@link WatcherState#STOPPED}; may not be {@code null}
*/
void shutDown(Runnable stoppedListener) {
assert stoppedListener != null;
logger.info("stopping watch service; reason [shutdown initiated]");
executionService.pause(stoppedListener);
triggerService.stop();
stopExecutor();
}
