Invalid number found: – 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 ” invalid number found: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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 “invalid number found:”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return Double.NaN;
 } else {
 try {
 return Double.parseDouble(stream.sval);
 } catch (NumberFormatException e) {
 throw new ElasticsearchParseException("invalid number found: " + stream.sval; stream.lineno());
 }
 }
 }
 throw new ElasticsearchParseException("expected number but found: " + tokenString(stream); stream.lineno());
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content