How To Solve Issues Related to Log – Triggered watches could not be deleted ; failure

Get an Elasticsearch Check-Up


Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

ES Check Up

Elasticsearch Error Guide In Page Navigation :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check My Elasticsearch 


Troubleshooting background

To troubleshoot Elasticsearch log “Triggered watches could not be deleted ; failure” it’s important to know common problems related to Elasticsearch concepts: plugin. See below-detailed explanations complete with common problems, examples and useful tips.

Plugin in Elasticsearch

What it is

Plugins are used to extend the functionality of Elasticsearch. In addition to the core plugins available to you, it is possible to write custom plugins as well. Plugins are generated in a zip format with the mandatory file structure.

Examples:
  • Core Plugins: Xpack for Security and monitoring, Discovery plugins for EC2
  • Adding S3 plugin for storing snapshots on S3
sudo bin/elasticsearch-plugin install repository-s3
  • Adding HDFS plugin for storing snapshots on HDFS
sudo bin/elasticsearch-plugin install repository-hdfs
  • Removing a plugin
sudo bin/elasticsearch-plugin remove repository-hdfs
Notes:
  • Plugins are installed using the Elasticsearch-plugin script, which enables actions such as  listing, removing and installing plugins.
  • Core plugins can be installed simply by providing the name of the plugin to the Elasticsearch-plugin command.
  • You can also download the plugin manually and then install it using the elasticsearch-plugin install command, providing the file name/path of the plugin’s source file.
  • When a plugin is removed, you will need to restart the elasticsearch node(s) in order to complete the removal process.
Common Problems:
  • You need to install the required plugins in your Elasticsearch deployment before moving it to production machines. (as it’s likely your production machines are behind a proxy and it’s very hard to get plugins installed behind a proxy).
  • The same is true when you are going to deploy elasticsearch using Docker images, you will most likely be rebuilding the standard image and including your required plugins in the custom docker build. Make sure the docker build is run on a build machine that is not behind a proxy, otherwise the plugin installation will fail during docker build.

Click here to get to our list of the Most frequent issues caused by Elasticsearch Plugins

DELETE Elasticsearch API

What is it

DELETE  is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document. 

Delete a document

DELETE /my_index/_doc/1
Notes
  • A delete request throws 404 error code if the document does not already exist in the index.
  • If you want to delete a set of documents that  matches a query, you need to use delete by query API.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

Illegal State Exception Is Preventi
discuss.elastic.co/t/illegal-state-exception-is-preventing-deletion-of-watches/55085

 

Github Issue Number 40053
github.com/elastic/elasticsearch/issues/40053

 


Log Context

Log ”Triggered watches could not be deleted ; failure” classname is Watcher.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

<pre class="wp-block-syntaxhighlighter-code">                         .filter(BulkItemResponse::isFailed)
                        .filter(r -> r.getIndex().startsWith(TriggeredWatchStoreField.INDEX_NAME))
                        .collect(Collectors.toMap(BulkItemResponse::getId; BulkItemResponse::getFailureMessage));
                    if (triggeredWatches.isEmpty() == false) {
                        String failure = triggeredWatches.values().stream().collect(Collectors.joining("; "));
                        logger.error("triggered watches could not be deleted {}; failure [{}]";
                            triggeredWatches.keySet(); Strings.substring(failure; 0; 2000));
                    }

                    Map<String; String> overwrittenIds = Arrays.stream(response.getItems())
                        .filter(BulkItemResponse::isFailed)




</pre>

About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?