Triggered watches could not be deleted ; failure – How to solve related issues

Average Read Time

2 Mins

Triggered watches could not be deleted ; failure – 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 ” Triggered watches could not be deleted ; failure ” 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 “Triggered watches could not be deleted {}; failure [{}]” classname is Watcher.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         .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 overwrittenIds = Arrays.stream(response.getItems())
                        .filter(BulkItemResponse::isFailed)




 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content