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

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Primary-replica resync completed with operations ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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";


Run the Check-Up to get a customized report like this:

Analyze your cluster