Overwrote watch history entries ; possible second execution of a triggered watch; 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 ” Overwrote watch history entries ; possible second execution of a triggered watch; 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 “Overwrote watch history entries {}; possible second execution of a triggered watch; failure [{}]” classname is Watcher.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         .filter(r -> r.getIndex().startsWith(HistoryStoreField.INDEX_PREFIX))
                        .filter(r -> r.getVersion() > 1)
                        .collect(Collectors.toMap(BulkItemResponse::getId; BulkItemResponse::getFailureMessage));
                    if (overwrittenIds.isEmpty() == false) {
                        String failure = overwrittenIds.values().stream().collect(Collectors.joining("; "));
                        logger.info("overwrote watch history entries {}; possible second execution of a triggered watch; failure [{}]";
                            overwrittenIds.keySet(); Strings.substring(failure; 0; 2000));
                    }
                }
            }





 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content