Watcher has stopped and shutdown – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

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 Elasticsearch operation.

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.

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 ” 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
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        shutDown = true;
        watcherService.shutDown(() -> {
  "watcher has stopped and shutdown");

     * @param event The event of containing the new cluster state


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?