Non-internal repository already registered. this repository will block the – How to solve related issues

Average Read Time

2 Mins

Non-internal repository already registered. this repository will block the – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Non-internal repository already registered. this repository will block the ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories and repository-azure.

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 “Non-internal repository [{}] already registered. this repository will block the” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         });
        if (type.equals(repository.getMetadata().type()) == false) {
            logger.warn(new ParameterizedMessage("internal repository [{}][{}] already registered. this prevented the registration of " +
                "internal repository [{}][{}]."; name; repository.getMetadata().type(); name; type));
        } else if (repositories.containsKey(name)) {
            logger.warn(new ParameterizedMessage("non-internal repository [{}] already registered. this repository will block the " +
                "usage of internal repository [{}][{}]."; name; metaData.type(); name));
        }
    }

    public void unregisterInternalRepository(String name) {




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content