Already primary; can’t move to primary – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Already primary; can’t move to primary ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, routing.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Already primary; can’t move to primary”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* @throws IllegalShardRoutingStateException if shard is already a primary
 public ShardRouting moveActiveReplicaToPrimary() {
 assert active() : "expected an active shard " + this;
 if (primary) {
 throw new IllegalShardRoutingStateException(this; "Already primary; can't move to primary");
 return new ShardRouting(


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content