Cluster state update after successful shard clone failed – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch attempts to update the cluster state after successfully cloning a shard, but the update fails. This could be due to network issues, node failures, or insufficient resources. To resolve this, you can try the following: 1) Check the network connectivity between the nodes; 2) Verify the health of the nodes in the cluster; 3) Ensure there are sufficient resources (CPU, memory, disk space) available for the operation; 4) Check the OpenSearch logs for more detailed error information; 5) Retry the operation after addressing the identified issues.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Cluster state update after successful shard clone [{}] failed ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster, shard.

Log Context

Log “Cluster state update after successful shard clone [{}] failed” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                                        e -> {
                                            logger.warn("Cluster state update after successful shard clone [{}] failed"; repoShardId);
                                    () -> currentlyCloning.remove(repoShardId)


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?

Get expert answers on Elasticsearch/OpenSearch