Failed to parse object: Expected START_OBJECT but was: – 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 object: Expected START_OBJECT but was: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest-high-level and client.

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 object: Expected START_OBJECT but was:”classname  is GroupConfig.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// be parsing friendly; whether the token needs to be advanced or not (similar to what ObjectParser does)
 XContentParser.Token token;
 if (parser.currentToken() != XContentParser.Token.START_OBJECT) {
 token = parser.nextToken();
 if (token != XContentParser.Token.START_OBJECT) {
 throw new ParsingException(parser.getTokenLocation(); "Failed to parse object: Expected START_OBJECT but was: " + token);
 }
 } 
 while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 ensureExpectedToken(XContentParser.Token.FIELD_NAME; token; parser::getTokenLocation);

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content