Indices options xcontent did not contain – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-8.9

Briefly, this error occurs when Elasticsearch is unable to find the expected content in the indices options during a request. This could be due to incorrect formatting, missing data, or a bug in the software. To resolve this issue, you can try the following: 1) Check and correct the formatting of your request. 2) Ensure all necessary data is included in the indices options. 3) Update Elasticsearch to the latest version to fix any potential bugs.

This guide will help you check for common problems that cause the log ” indices options xcontent did not contain ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices.

Log Context

Log “indices options xcontent did not contain” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ElasticsearchParseException("could not read indices options. unexpected object field [" + currentFieldName + "]");
 }  if (wildcardStates == null) {
 throw new ElasticsearchParseException("indices options xcontent did not contain " + EXPAND_WILDCARDS_FIELD.getPreferredName());
 if (ignoreUnavailable == null) {
 throw new ElasticsearchParseException(
 "indices options xcontent did not contain " + IGNORE_UNAVAILABLE_FIELD.getPreferredName()


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?