Failed marking repository state as corrupted – Elasticsearch Error How To Solve Related Issues

Failed marking repository state as corrupted – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “Failed marking repository state as corrupted” 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, 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 OrientDB corruption state in Nexus Repository version 3.2.0-01 -views 16,295 ,score 18

Corrupted elastic index – Elasticsearch – Discuss the Elastic Stack  

Find Configuration Errors

Analyze Now