Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
This guide will help you check for common problems that cause the log ” could not read indices options. unexpected object field ” + currentFieldName + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices.
Log Context
Log “could not read indices options. unexpected object field [” + currentFieldName + “]”classname is IndicesOptions.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
throw new ElasticsearchParseException(
"could not read indices options. unexpected index option [" + currentFieldName + "]"
);
}
} else {
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());
