Restore failed – 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, check the compatibility of the snapshot with your current Elasticsearch version, and verify the integrity of your snapshot files. If the snapshot is corrupted, you may need to create a new one. Also, check the Elasticsearch logs for more specific error messages that can guide you to the root cause.

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

Log Context

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

 indexShard.postRecovery("restore done");
 }; e -> listener.onFailure(new IndexShardRestoreFailedException(shardId; "restore failed"; e)));
 try {
 final ShardId snapshotShardId;