Internal repository already registered. this prevented the registration of – How to solve related issues

Internal repository already registered. this prevented the registration of – 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 ” Internal repository already registered. this prevented the registration of ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Internal repository [{}][{}] already registered. this prevented the registration of” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         Repository repository = internalRepositories.computeIfAbsent(name; (n) -> {
            logger.debug("put internal repository [{}][{}]"; name; type);
            return createRepository(metaData; internalTypesRegistry);
        });
        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));
        }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster