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 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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories.

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 “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) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content