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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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.

Log Context

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

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


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content