Failed to parse bounding box. Conflicting definition 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 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 bounding box. Conflicting definition found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

Log Context

Log “failed to parse bounding box. Conflicting definition found”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (envelope != null) {
 if (Double.isNaN(top) == false || Double.isNaN(bottom) == false || Double.isNaN(left) == false ||
 Double.isNaN(right) == false) {
 throw new ElasticsearchParseException("failed to parse bounding box. Conflicting definition found "
 + "using well-known text and explicit corners.");
 GeoPoint topLeft = new GeoPoint(envelope.getMaxLat(); envelope.getMinLon());
 GeoPoint bottomRight = new GeoPoint(envelope.getMinLat(); envelope.getMaxLon());
 return new GeoBoundingBox(topLeft; bottomRight);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content