Could not read search request unexpected token token – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch receives a search request that contains an unexpected token. This usually happens due to a malformed query, where the syntax doesn’t match what Elasticsearch expects. To resolve this issue, you should first check the syntax of your search request. Ensure that all brackets, quotation marks, and other special characters are correctly placed. Also, verify that the field names and values in your query match those in your Elasticsearch index. If the error persists, consider simplifying your query to identify the problematic part.

This guide will help you check for common problems that cause the log ” could not read search request. unexpected token [” + token + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, search, request.

Log Context

Log “could not read search request. unexpected token [” + token + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ElasticsearchParseException(
 "could not read search request. unexpected boolean field [" + currentFieldName + "]"
 } else {
 throw new ElasticsearchParseException("could not read search request. unexpected token [" + token + "]");
 }  if (searchSource == null) {
 searchSource = BytesArray.EMPTY;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?