Could not parse action /. unexpected number field – How to solve this Elasticsearch error

Could not parse action /. unexpected number field – 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 action /. unexpected number field ” 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: index 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 [{}] action [{}/{}]. unexpected number field [{}]”classname  is IndexAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  } else if (token == XContentParser.Token.VALUE_NUMBER) {
  if (Field.TIMEOUT.match(currentFieldName; parser.getDeprecationHandler())) {
  timeout = timeValueMillis(parser.longValue());
  } else {
  throw new ElasticsearchParseException("could not parse [{}] action [{}/{}]. unexpected number field [{}]"; TYPE;
  watchId; actionId; currentFieldName);
  }
  } else if (token == XContentParser.Token.VALUE_STRING) {
  if (Field.DOC_ID.match(currentFieldName; parser.getDeprecationHandler())) {
  docId = parser.text();

Run the Check-Up to get a customized report like this:

check-up-dashboard illustration

Try The Tool