Cannot normalize the point – not 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 ” cannot normalize the point – not a number ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

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 “cannot normalize the point – not a number”classname  is GeoPointFieldMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

@Override
 public void normalize(String name) {
 if (isNormalizable(lat()) && isNormalizable(lon())) {
 GeoUtils.normalizePoint(this);
 } else {
 throw new ElasticsearchParseException("cannot normalize the point - not a number");
 }
 } 
 @Override
 public boolean isNormalizable(double coord) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content