Primary-replica resync completed with operations – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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 Elasticsearch concepts: index and shard.

Log Context

Log “Primary-replica resync completed with {} operations” classname is
We extracted the following from Elasticsearch 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";
                                        boolean resyncCompleted =
                                            primaryReplicaResyncInProgress.compareAndSet(true; false);
                                        assert resyncCompleted : "primary-replica resync finished but was not started";


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content