Cannot normalize the point – not a number – Elasticsearch Error How To Solve Related Issues

Cannot normalize the point – not a number – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “cannot normalize the point – not 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: index.

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”cannot normalize the point – not a number”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How to normalize score across multiple search results -views 61 ,score 4

Search by phone number – Elasticsearch – Discuss the Elastic Stack  



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now