Failed to restore snapshot snapshotId – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to restore a snapshot due to reasons like insufficient disk space, incompatible versions between the snapshot and the current Elasticsearch, or corrupted snapshot files. To resolve this, ensure you have enough disk space and that the snapshot version is compatible with your Elasticsearch version. If the snapshot files are corrupted, try restoring from a different snapshot. If the issue persists, consider reindexing your data.

This guide will help you check for common problems that cause the log ” failed to restore snapshot [” + snapshotId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, restore, snapshot, repositories.

Log Context

Log “failed to restore snapshot [” + snapshotId + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 RecoveryState recoveryState;
 ActionListener listener
 ) {
 final ShardId shardId = store.shardId();
 final ActionListener restoreListener = listener.delegateResponse(
 (l; e) -> l.onFailure(new IndexShardRestoreFailedException(shardId; "failed to restore snapshot [" + snapshotId + "]"; e))
 final Executor executor = threadPool.executor(ThreadPool.Names.SNAPSHOT);
 final BlobContainer container = shardContainer(indexId; snapshotShardId);
 synchronized (ongoingRestores) {
 if (store.isClosing()) {