Briefly, this error occurs when the Elasticsearch Watcher, a tool for alerting and monitoring, encounters an issue that forces it to stop and shutdown. This could be due to a variety of reasons such as insufficient resources, configuration errors, or underlying system issues. To resolve this, you can try restarting the Watcher, checking the system logs for any specific error messages, ensuring that the Elasticsearch cluster has sufficient resources, and verifying the Watcher’s configuration settings. If the problem persists, consider upgrading Elasticsearch to the latest version or reaching out to the support team.
This guide will help you check for common problems that cause the log ” watcher has stopped and shutdown ” 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 stopped and shutdown” classname is WatcherLifeCycleService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
this.state.set(WatcherState.STOPPING);
shutDown = true;
clearAllocationIds();
watcherService.shutDown(() -> {
this.state.set(WatcherState.STOPPED);
logger.info("watcher has stopped and shutdown");
});
}
/**
* @param event The event of containing the new cluster state
[ratemypost]
