Snapshot failed – How to solve this Elasticsearch error

Average Read Time

2 Mins

Snapshot failed – How to solve this Elasticsearch error

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 ” snapshot failed ” 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: recovery, indices and snapshot.

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”snapshot failed”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final Engine.IndexCommitRef safeCommitRef;
  try {
  safeCommitRef = shard.acquireSafeIndexCommit();
  } catch (final Exception e) {
  throw new RecoveryEngineException(shard.shardId(); 1; "snapshot failed"; e);
  // Try and copy enough operations to the recovering peer so that if it is promoted to primary then it has a chance of being
  // able to recover other replicas using operations-based recoveries. If we are not using retention leases then we
  // conservatively copy all available operations. If we are using retention leases then "enough operations" is just the


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

Analyze your cluster