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

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to perform an operation on a repository that is not in a ‘started’ state. This could be due to the repository being in the process of initialization or being shut down. To resolve this issue, you can either wait for the repository to reach the ‘started’ state if it’s initializing, or restart the repository if it’s shut down. Additionally, check the repository’s configuration settings to ensure it’s set to automatically start upon system boot.

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: blobstore, repository, repositories.

Log Context

Log “repository is not in started state” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  private RepositoryException notStartedException() {
 return new RepositoryException(; "repository is not in started state");
 }  // Listener used to ensure that repository data is only initialized once in the cluster state by #initializeRepoGenerationTracking
 private ListenableActionFuture repoDataInitialized;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?