Index index wasn t fully snapshotted – cannot restore – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.14-8.9

Briefly, this error occurs when Elasticsearch tries to restore an index from a snapshot, but the snapshot of the index wasn’t fully completed. This could be due to an interruption during the snapshot process or insufficient disk space. To resolve this issue, you can try to create a new snapshot ensuring there’s enough disk space and no interruptions during the process. Alternatively, check if there are other successful snapshots of the same index that can be restored.

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” class name 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;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?