Failed marking repository state as corrupted – How to solve this Elasticsearch error

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 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 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 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 marking repository state as corrupted”classname  is BlobStoreRepository.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

metadata.name(); RepositoryData.CORRUPTED_REPO_GEN; repoState.pendingGeneration())).build()).build();
  }
 
  @Override
  public void onFailure(String source; Exception e) {
  listener.onFailure(new RepositoryException(metadata.name(); "Failed marking repository state as corrupted";
  ExceptionsHelper.useOrSuppress(e; originalException)));
  }
 
  @Override
  public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {

 

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

Analyze your cluster