Can t create clone of shardId for snapshot – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-7.13

Briefly, this error occurs when Elasticsearch is unable to clone a shard for creating a snapshot. This could be due to insufficient disk space, network issues, or problems with the underlying file system. To resolve this, you can try freeing up disk space, checking network connectivity, or repairing the file system. Additionally, ensure that the Elasticsearch cluster is in a healthy state and that the shard is not corrupted. If the shard is corrupted, you may need to restore it from a previous snapshot.

This guide will help you check for common problems that cause the log ” Can’t create clone of [” + shardId + “] for snapshot [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, shard, snapshot, blobstore.

Log Context

Log “Can’t create clone of [” + shardId + “] for snapshot [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (sourceFiles != null && existingTargetFiles != null) {
 if (sourceFiles == null) {
 throw new RepositoryException(; "Can't create clone of [" + shardId + "] for snapshot ["
 + target + "]. The source snapshot [" + source + "] was not found in the shard metadata.");
 if (existingTargetFiles != null) {
 if (existingTargetFiles.isSame(sourceFiles)) {
 return new ShardSnapshotResult(