Failed to parse search source. source must be an object; but found instead – 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 search source. source must be an object; but found instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest, source, search and plugin.

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 search source. source must be an object; but found [{}] instead”classname  is RestGraphAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try (XContentParser parser = request.contentOrSourceParamParser()) { 
 XContentParser.Token token = parser.nextToken(); 
 if (token != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("failed to parse search source. source must be an object; but found [{}] instead";
 token.name());
 }
 parseHop(parser; currentHop; graphRequest);
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content