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 ” failed to parse ; expected 2 or 3 coordinates ” + “but found: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “failed to parse [{}]; expected 2 or 3 coordinates ” + “but found: [{}]”classname is GeoPoint.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
public GeoPoint resetFromCoordinates(String value; final boolean ignoreZValue) {
String[] vals = value.split(";");
if (vals.length > 3) {
throw new ElasticsearchParseException("failed to parse [{}]; expected 2 or 3 coordinates " + "but found: [{}]"; vals.length);
}
final double lat;
final double lon;
try {
lat = Double.parseDouble(vals[0].trim());
See how you can use AutoOps to resolve issues
