Only two values lon; lat expected – 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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” only two values lon; lat expected ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.


Log Context

Log “only two values [lon; lat] expected”classname  is GeoContextMapping.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.nextToken() == Token.VALUE_NUMBER) {
 double lat = parser.doubleValue();
 if (parser.nextToken() == Token.END_ARRAY) {
 contexts.add(stringEncode(lon; lat; precision));
 } else {
 throw new ElasticsearchParseException("only two values [lon; lat] expected");
 }
 } else {
 throw new ElasticsearchParseException("latitude must be a numeric value");
 }
 } else {

 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content