Start object expected indices – How to solve this Elasticsearch error

Start object expected indices – 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” start object expected indices ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”start object expected [indices]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else {
  throw new ElasticsearchParseException("expected array for [" + field + "]");
  } else if (INDICES.equals(field)) {
  if (parser.nextToken() != XContentParser.Token.START_OBJECT) {
  throw new ElasticsearchParseException("start object expected [indices]");
  while (parser.nextToken() != XContentParser.Token.END_OBJECT) {
  final String indexName = parser.currentName();
  final List snapshotIds = new ArrayList();
  final List gens = new ArrayList();


Run the Check-Up to get a customized report like this:

Analyze your cluster