Failed marking repository state as corrupted – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed marking repository state as corrupted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository and blobstore.

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 “Failed marking repository state as corrupted”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :; RepositoryData.CORRUPTED_REPO_GEN; repoState.pendingGeneration())).build()).build();
 public void onFailure(String source; Exception e) {
 listener.onFailure(new RepositoryException(; "Failed marking repository state as corrupted";
 ExceptionsHelper.useOrSuppress(e; originalException)));
 public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content