Failed to perform snapshot index files – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.5

Briefly, this error occurs when Elasticsearch is unable to create a snapshot of the index files. This could be due to insufficient permissions, lack of storage space, or network connectivity issues. To resolve this, ensure that the Elasticsearch process has the necessary permissions to write to the snapshot directory. Also, check if there’s enough storage space available and if the network connection to the snapshot repository is stable. If the issue persists, consider checking the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Failed to perform snapshot (index files) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, snapshot, blobstore.

Log Context

Log “Failed to perform snapshot (index files)” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new IllegalStateException("Store is closed already");
 } catch (IOException e) {
 throw new IndexShardSnapshotFailedException(shardId; "Failed to perform snapshot (index files)"; e);
 }  @Override
 public void onFailure(Exception e) {


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?