Cannot restore partial index – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.6-7.13

Briefly, this error occurs when you try to restore an index from a snapshot, but the index was not fully saved due to an interruption or failure during the snapshot process. This results in a partial index that cannot be restored. To resolve this issue, you can either retry the snapshot process ensuring there are no interruptions, or restore from a previous successful snapshot. If neither is possible, you may need to rebuild the index from your original data source.

This guide will help you check for common problems that cause the log ” cannot restore partial index [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, restore.

Log Context

Log “cannot restore partial index [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 "with same name already exists in the cluster. Either close or delete the existing index or restore the " +
 "index under a different name by providing a rename pattern and replacement name");
 // Index exist - checking if it's partial restore
 if (partial) {
 throw new SnapshotRestoreException(snapshot; "cannot restore partial index [" + renamedIndex
 + "] because such index already exists");
 // Make sure that the number of shards is the same. That's the only thing that we cannot change
 if (currentIndexMetadata.getNumberOfShards() != snapshotIndexMetadata.getNumberOfShards()) {
 throw new SnapshotRestoreException(snapshot;


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?