Repository type repositoryMetadata type does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.14-8.9

Briefly, this error occurs when Elasticsearch cannot find the repository type specified in the repository metadata. This could be due to a typo in the repository type name or the repository plugin not being installed. To resolve this issue, you can check the repository type name for any spelling errors. If the name is correct, ensure that the necessary repository plugin is installed and enabled. If the plugin is missing, install it and restart Elasticsearch. If the plugin is disabled, enable it and try again.

This guide will help you check for common problems that cause the log ” repository type [” + repositoryMetadata.type() + “] does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository, metadata, repositories.

Log Context

Log “repository type [” + repositoryMetadata.type() + “] does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public Repository createRepository(RepositoryMetadata repositoryMetadata) {
 return createRepository(repositoryMetadata; typesRegistry; RepositoriesService::throwRepositoryTypeDoesNotExists);
 }  private static Repository throwRepositoryTypeDoesNotExists(RepositoryMetadata repositoryMetadata) {
 throw new RepositoryException(; "repository type [" + repositoryMetadata.type() + "] does not exist");
 }  private static Repository createUnknownTypeRepository(RepositoryMetadata repositoryMetadata) {
 "[{}] repository type [{}] is unknown; ensure that all required plugins are installed on this node";


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?