How To Solve Issues Related to Log – Unable to find watch in watch index; perhaps it has been deleted

How To Solve Issues Related to Log – Unable to find watch in watch index; perhaps it has been deleted

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Unable to find watch in watch index; perhaps it has been deleted” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

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));




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Unable To Find Watch In The Watch S  

How To Fix A Stuck Watch And Anothe  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now