Failed to update watch record – 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 ” Failed to update watch record ” 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 “Failed to update watch record [{}]” classname is ExecutionService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             historyStore.forcePut(record);
                        } else {
                            historyStore.put(record);
                        }
                    } catch (Exception e) {
                        logger.error((Supplier>) () -> new ParameterizedMessage("failed to update watch record [{}]"; ctx.id()); e);
                        // TODO log watch record in logger; when saving in history store failed; otherwise the info is gone!
                    }
                }

                triggeredWatchStore.delete(ctx.id());




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content