Failed to restore snapshot ” + snapshotId + ” – 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.

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: repositories, restore, snapshot, blobstore.

Log Context

Log “failed to restore snapshot [” + snapshotId + “]”classname  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()) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content