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.
Overview
Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.
Examples
When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.
GET my_documents/_search
A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.
{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}Notes and good things to know
- Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
- There are two phases of search: the query phase and the fetch phase.
- In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list.
- In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
- A coordinating node needs enough memory and CPU in order to handle the fetch phase.
Log Context
Log “could not read search request. unexpected token [” + token + “]” class name is WatcherSearchTemplateRequest.java. 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;
