Primary-replica resync completed with operations – 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 the primary shard and its replicas have completed a resynchronization process. This is not an error but an informational message indicating that the resync operation has been completed successfully. The number inside the {} brackets shows the number of operations that were performed during the resync. If you’re seeing this message frequently or at unexpected times, it might indicate an issue with your cluster stability. To resolve this, ensure your cluster is properly sized for your workload, monitor your cluster’s health, and adjust your shard allocation settings if necessary.

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 ” primary-replica resync completed with {} operations ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: index, shard.

Log Context

Log “primary-replica resync completed with {} operations” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                            replicationTracker.updateLocalCheckpoint(currentRouting.allocationId().getId(); getLocalCheckpoint());
                            primaryReplicaSyncer.accept(this; new ActionListener() {
                                public void onResponse(ResyncTask resyncTask) {
                          "primary-replica resync completed with {} operations"; resyncTask.getResyncedOperations());
                                    boolean resyncCompleted = primaryReplicaResyncInProgress.compareAndSet(true; false);
                                    assert resyncCompleted : "primary-replica resync finished but was not started";



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