Repository is not in started state – How to solve this Elasticsearch error

Average Read Time

2 Mins

Repository is not in started state – 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 ” repository is not in started state ” 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 “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;

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content