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 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. 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 “[{}]] 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 [{}]; " +


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content