Stopping watch service; reason shutdown initiated – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 :

     /**
     * shuts down the trigger service as well to make sure there are no lingering threads
     * also no need to check anything; as this is final; we just can go to status STOPPED
     */
    void shutDown() {
        logger.info("stopping watch service; reason [shutdown initiated]");
        executionService.pause();
        triggerService.stop();
        stopExecutor();
        logger.debug("watch service has stopped");
    }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content