Could not read search request. unexpected index option – 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 ” could not read search request. unexpected index option ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, 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 “could not read search request. unexpected index option [“classname  is WatcherSearchTemplateRequest.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (IGNORE_UNAVAILABLE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 ignoreUnavailable = parser.booleanValue();
 } else if (ALLOW_NO_INDICES_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 allowNoIndices = parser.booleanValue();
 } else {
 throw new ElasticsearchParseException("could not read search request. unexpected index option [" +
 currentFieldName + "]");
 }
 } else {
 throw new ElasticsearchParseException("could not read search request. unexpected object field [" +
 currentFieldName + "]");

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content