Repository is not in started state – Elasticsearch Error How To Solve Related Issues


Repository is not in started state – Elasticsearch Error How To Solve Related Issues

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

if (store == null) {
  synchronized (lock) {
  store = blobStore.get();
  if (store == null) {
  if (lifecycle.started() == false) {
  throw new RepositoryException(metadata.name(); "repository is not in started state");
  }
  try {
  store = createBlobStore();
  } catch (RepositoryException e) {
  throw e;

 

Optimize Elasticsearch Performance

Try The Tool