must be a number – How to solve this Elasticsearch error

must be a number – 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 ” must be a number ” 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: 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”[{}]] must be a number”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

"must be between -3.4028234663852886E38 and 3.4028234663852886E38";
  } catch (NumberFormatException ex) {
  throw new ElasticsearchParseException("[{}]] must be a number"; X_FIELD.getPreferredName());
  try {
  y = Float.parseFloat(vals[1].trim());
  if (Float.isFinite(y) == false) {
  throw new ElasticsearchParseException("invalid [{}] value [{}]; " +


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

Analyze your cluster