Could not parse input for watch . failed to parse . must be a – How to solve this Elasticsearch error

Could not parse input for watch . failed to parse . must be a – 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 Error 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 input for watch . failed to parse . must be a ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”could not parse [{}] input for watch [{}]. failed to parse [{}]. must be a”classname  is SearchInput.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

timeout = WatcherDateTimeUtils.parseTimeValue(parser; Field.TIMEOUT_HUMAN.toString());
  } else if (Field.DYNAMIC_NAME_TIMEZONE.match(currentFieldName; parser.getDeprecationHandler())) {
  if (token == XContentParser.Token.VALUE_STRING) {
  dynamicNameTimeZone = DateUtils.of(parser.text());
  } else {
  throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. failed to parse [{}]. must be a " +
  "string value (e.g. 'UTC' or '+01:00')."; TYPE; watchId; currentFieldName);
  }
  } else {
  throw new ElasticsearchParseException("could not parse [{}] input for watch [{}]. unexpected token [{}]"; TYPE; watchId;
  token);

Run the Check-Up to get customized recommendations like this:

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized recommendation]

 

Optimize Elasticsearch Performance

Try The Tool