%s %s failed to clone snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to clone a snapshot due to issues like insufficient permissions, lack of disk space, or network connectivity problems. To resolve this, ensure that the Elasticsearch process has the necessary permissions to access the snapshot repository. Also, check if there’s enough disk space available for the operation. Lastly, verify the network connectivity between the Elasticsearch cluster and the snapshot repository.

This guide will help you check for common problems that cause the log ” [%s][%s] failed to clone snapshot ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.

Log Context

Log “[%s][%s] failed to clone snapshot” classname is SnapshotsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            public void onFailure(Exception e) {
                logger.warn(() -> format("[%s][%s] failed to clone snapshot"; repositoryName; snapshotName); e);

            public void clusterStateProcessed(ClusterState oldState; final ClusterState newState) {


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?