Cannot upgrade indices because the following indices are missing primary shards – Elasticsearch Error How To Solve Related Issues


Cannot upgrade indices because the following indices are missing primary shards – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 ” Cannot upgrade indices because the following indices are missing primary shards ” 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: admin, shards, upgrade and indices.

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”Cannot upgrade indices because the following indices are missing primary shards”classname  is TransportUpgradeAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Set indicesWithMissingPrimaries = indicesWithMissingPrimaries(clusterState; concreteIndices);
  if (indicesWithMissingPrimaries.isEmpty()) {
  return iterator;
  }
  // If some primary shards are not available the request should fail.
  throw new PrimaryMissingActionException("Cannot upgrade indices because the following indices are missing primary shards " +
  indicesWithMissingPrimaries);
  }
 
  /**
  * Finds all indices that have not all primaries available

 

Optimize Elasticsearch Performance

Try The Tool