Failed to update snapshot in repository – How to solve this Elasticsearch error

Failed to update snapshot in repository – 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 ” failed to update snapshot in repository ” 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: repositories, repository, snapshot and blobstore.

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

// directory if all nodes are at least at version SnapshotsService#SHARD_GEN_IN_REPO_DATA_VERSION
  // If there are older version nodes in the cluster; we don't need to run this cleanup as it will have already happened
  // when writing the index-${N} to each shard directory.
  final boolean writeShardGens = SnapshotsService.useShardGenerations(repositoryMetaVersion);
  final Consumer onUpdateFailure =
  e -> listener.onFailure(new SnapshotException(; snapshotId; "failed to update snapshot in repository"; e));
  final Executor executor = threadPool.executor(ThreadPool.Names.SNAPSHOT);
  final boolean writeIndexGens = SnapshotsService.useIndexGenerations(repositoryMetaVersion);


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

Analyze your cluster