Repository type ” + repositoryMetadata.type() + ” does not exist – How to solve this Elasticsearch error

Average Read Time

2 Mins

Repository type ” + repositoryMetadata.type() + ” does not exist – How to solve this Elasticsearch error

Opster Team

March-22, 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 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: repositories, metadata, repository.

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 type [” + repositoryMetadata.type() + “] does not exist”classname  is RepositoriesService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new RepositoryException(repositoryMetadata.name(); "failed to create repository"; e);
 }
 } 
 private Repository throwRepositoryTypeDoesNotExists(RepositoryMetadata repositoryMetadata) {
 throw new RepositoryException(repositoryMetadata.name(); "repository type [" + repositoryMetadata.type() + "] does not exist");
 } 
 private Repository createUnknownTypeRepository(RepositoryMetadata repositoryMetadata) {
 logger.warn(
 "[{}] repository type [{}] is unknown; ensure that all required plugins are installed on this node";

 

Watch a demo of the Check-Up:

Analyze your cluster