Unable to find watch in watch index; perhaps it has been deleted – How to solve related issues

Average Read Time

2 Mins

Unable to find watch in watch index; perhaps it has been deleted – 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 ” Unable to find watch in watch index; perhaps it has been deleted ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “Unable to find watch [{}] in watch index; perhaps it has been deleted” classname is ExecutionService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        DateTime now = new DateTime(clock.millis(); UTC);
        for (TriggerEvent event : events) {
            GetResponse response = getWatch(event.jobName());
            if (response.isExists() == false) {
                logger.warn("unable to find watch [{}] in watch index; perhaps it has been deleted"; event.jobName());
                continue;
            }
            TriggeredExecutionContext ctx = new TriggeredExecutionContext(event.jobName(); now; event; defaultThrottlePeriod);
            contexts.add(ctx);
            triggeredWatches.add(new TriggeredWatch(ctx.id(); event));




 

Run the Check-Up to get a customized report like this:

Analyze your cluster