Index ” + index + ” wasn’t fully snapshotted – cannot restore – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” index ” + index + ” wasn’t fully snapshotted – cannot restore ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: restore, index.

Log Context

Log “index [” + index + “] wasn’t fully snapshotted – cannot restore”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Make sure that index was fully snapshotted
 if (failed(snapshotInfo; index)) {
 if (request.partial()) {
 return true;
 } else {
 throw new SnapshotRestoreException(snapshot; "index [" + index + "] wasn't fully snapshotted - cannot restore");
 } else {
 return false;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content