Failed to parse ; expected 2 or 3 coordinates – 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 ” failed to parse ; expected 2 or 3 coordinates ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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 “failed to parse [{}]; expected 2 or 3 coordinates”classname  is 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 {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content