Snapshot could not be read – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to read a snapshot due to issues like incorrect file permissions, corrupted snapshot files, or the snapshot file being deleted or moved. To resolve this, you can check and correct the file permissions, restore the snapshot from a backup if it’s deleted or moved, or recreate the snapshot if it’s corrupted. Also, ensure that the Elasticsearch cluster has the necessary read permissions for the repository where the snapshot is stored.

This guide will help you check for common problems that cause the log ” Snapshot could not be read ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, snapshot, repositories.

Log Context

Log “Snapshot could not be read” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } catch (IOException | NotXContentException ex) {
 failure = new SnapshotException(; snapshotId; "failed to get snapshot info" + snapshotId; ex);
 } catch (Exception e) {
 failure = e instanceof SnapshotException
 ? e
 : new SnapshotException(; snapshotId; "Snapshot could not be read"; e);
 if (failure != null) {
 if (context.abortOnFailure()) {


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?