Not starting watcher; upgrade API run required: .watches; .triggeredwatches – 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 ” Not starting watcher; upgrade API run required: .watches; .triggeredwatches ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and upgrade.

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 “Not starting watcher; upgrade API run required: .watches[{}]; .triggered_watches[{}]” classname is WatcherService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         boolean isIndexInternalFormatWatchIndex = watcherIndexMetaData == null ||
            UpgradeField.checkInternalIndexFormat(watcherIndexMetaData);
        boolean isIndexInternalFormatTriggeredWatchIndex = triggeredWatchesIndexMetaData == null ||
            UpgradeField.checkInternalIndexFormat(triggeredWatchesIndexMetaData);
        if (isIndexInternalFormatTriggeredWatchIndex == false || isIndexInternalFormatWatchIndex == false) {
            logger.warn("not starting watcher; upgrade API run required: .watches[{}]; .triggered_watches[{}]";
                isIndexInternalFormatWatchIndex; isIndexInternalFormatTriggeredWatchIndex);
            return false;
        }

        try {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content