Could not read repository data from index blob – Elasticsearch Error How To Solve Related Issues



Could not read repository data from index blob – 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 “could not read repository data from index blob” 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, index.


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”could not read repository data from index blob”classname  is BlobStoreRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// operations must start from the EMPTY_REPO_GEN again
  if (latestKnownRepoGen.compareAndSet(indexGen; RepositoryData.EMPTY_REPO_GEN)) {
  logger.warn("Resetting repository generation tracker because we failed to read generation [" + indexGen + "]"; ioe);
  }
  }
  throw new RepositoryException(metadata.name(); "could not read repository data from index blob"; ioe);
  }
  }
 
  private static String testBlobPrefix(String seed) {
  return TESTS_FILE + seed;

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 ES-v5.0.1 throw java.lang.SecurityException while snapshot -views 546 

Plugin security policies not reliably being automatically loaded …  



Find Configuration Errors

Analyze Now