Illegal latitude value for – How to solve this Elasticsearch error

Illegal latitude value for – 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 ” illegal latitude value for ” 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: query and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”illegal latitude value [{}] for [{}]”classname  is GeoPolygonQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// validation was not available prior to 2.x; so to support bwc
  // percolation queries we only ignore_malformed on 2.x created indexes
  if (!GeoValidationMethod.isIgnoreMalformed(validationMethod)) {
  for (GeoPoint point : shell) {
  if (!GeoUtils.isValidLatitude(point.lat())) {
  throw new QueryShardException(context; "illegal latitude value [{}] for [{}]"; point.lat();
  GeoPolygonQueryBuilder.NAME);
  }
  if (!GeoUtils.isValidLongitude(point.lon())) {
  throw new QueryShardException(context; "illegal longitude value [{}] for [{}]"; point.lon();
  GeoPolygonQueryBuilder.NAME);

Run the Check-Up to get customized recommendations like this:

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized recommendation]

 

Optimize Elasticsearch Performance

Try The Tool