Snapshot should be performed only on primary – How to solve this Elasticsearch error

Average Read Time

2 Mins

Snapshot should be performed only on 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 ” snapshot should be performed only on primary ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.

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 “snapshot should be performed only on primary”classname  is SnapshotShardsService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ActionListener listener
 ) {
 try {
 final IndexShard indexShard = indicesService.indexServiceSafe(shardId.getIndex()).getShardOrNull(shardId.id());
 if (indexShard.routingEntry().primary() == false) {
 throw new IndexShardSnapshotFailedException(shardId; "snapshot should be performed only on primary");
 }
 if (indexShard.routingEntry().relocating()) {
 // do not snapshot when in the process of relocation of primaries so we won't get conflicts
 throw new IndexShardSnapshotFailedException(shardId; "cannot snapshot while relocating");
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content