Briefly, this error occurs when Elasticsearch’s built-in alerting feature, known as Watcher, is stopped. This could be due to a manual stop command, a system shutdown, or an internal error. To resolve this, you can restart the Watcher service manually using the Elasticsearch API. If the issue persists, check the Elasticsearch logs for any underlying issues that may be causing the Watcher service to stop. Ensure that your Elasticsearch cluster has sufficient resources and is properly configured to avoid such issues.
This guide will help you check for common problems that cause the log ” stopping watch service; reason [{}] ” 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 [{}]” 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}
*/
public void stop(String reason; Runnable stoppedListener) {
assert stoppedListener != null;
logger.info("stopping watch service; reason [{}]"; reason);
executionService.pause(stoppedListener);
triggerService.pauseExecution();
}
/**
[ratemypost]
