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

Opster Team

August-23, Version: 6.8-7.13

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to fully snapshot an index, which is a backup of the data. This could be due to insufficient disk space, network issues, or the index being deleted during the snapshot process. To resolve this, ensure there’s enough disk space and a stable network connection. Also, avoid deleting indices during snapshotting. If the issue persists, consider reindexing your data or creating a new snapshot repository.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

Log “index [” + index + “] wasn’t fully snapshotted – cannot ” 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 " +
 } 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?