Can t clone index – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-7.13

Briefly, this error occurs when Elasticsearch is unable to duplicate an existing index, possibly due to insufficient permissions, lack of disk space, or the index being open. To resolve this, you can ensure the user has the necessary permissions, free up or add more disk space, or close the index before cloning. Additionally, check for any underlying system or network issues that might be causing the problem.

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

Log Context

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

 final GroupedActionListener> shardCountListener =
 new GroupedActionListener<>(allShardCountsListener; indices.size());
 snapshotInfoListener.whenComplete(snapshotInfo -> {
 for (IndexId indexId : indices) {
 if (RestoreService.failed(snapshotInfo; indexId.getName())) {
 throw new SnapshotException(targetSnapshot; "Can't clone index [" + indexId +
 "] because its snapshot was not successful.");
 // 2. step; load the number of shards we have in each index to be cloned from the index metadata.
 repository.getRepositoryData(ActionListener.wrap(repositoryData -> {


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?