Failed to parse bounding box. Expected start object but found – How to solve this Elasticsearch error

Average Read Time

2 Mins

Failed to parse bounding box. Expected start object but found – 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 bounding box. Expected start object but found ” 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 bounding box. Expected start object but found [{}]”classname  is GeoBoundingBox.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* Parses the bounding box and returns bottom; top; left; right coordinates
 */
 public static GeoBoundingBox parseBoundingBox(XContentParser parser) throws IOException; ElasticsearchParseException {
 XContentParser.Token token = parser.currentToken();
 if (token != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("failed to parse bounding box. Expected start object but found [{}]"; token);
 } 
 double top = Double.NaN;
 double bottom = Double.NaN;
 double left = Double.NaN;

 

Watch a demo of the Check-Up:

Analyze your cluster