Could not parse watch with id – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” Could not parse watch with id ” 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 “Could not parse watch with id [{}]”classname  is WatcherIndexingListener.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 } else {
 logger.debug("watch [{}] should not be triggered. watcher state [{}]"; watch.id(); currentState);
 }
 } catch (IOException e) {
 throw new ElasticsearchParseException("Could not parse watch with id [{}]"; e; operation.id());
 }
 }
 } 
 /**

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content