Start array expected snapshots – How to solve this Elasticsearch error

Average Read Time

2 Mins

Start array expected snapshots – 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 array expected snapshots ” 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 array expected [snapshots]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  if (INDEX_ID.equals(indexMetaFieldName)) {
  indexId = new IndexId(indexName; parser.text());
  } else if (SNAPSHOTS.equals(indexMetaFieldName)) {
  if (parser.currentToken() != XContentParser.Token.START_ARRAY) {
  throw new ElasticsearchParseException("start array expected [snapshots]");
  while (parser.nextToken() != XContentParser.Token.END_ARRAY) {
  String uuid = null;
  // the old format pre 5.4.1 which contains the snapshot name and uuid
  if (parser.currentToken() == XContentParser.Token.START_OBJECT) {


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

Analyze your cluster