Internal repository already registered this prevented the registration of – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.13

Briefly, this error occurs when there’s an attempt to register a repository in Elasticsearch that already exists. This could be due to a configuration issue or a script running multiple times. To resolve this, you can either delete the existing repository using the DELETE repository API before re-registering it, or check your scripts and configurations to ensure they’re not attempting to register the same repository multiple times. Also, ensure that the repository name is unique each time you’re creating a new one.

This guide will help you check for common problems that cause the log ” internal repository [{}][{}] already registered. this prevented the registration of ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository.

Log Context

Log “internal repository [{}][{}] already registered. this prevented the registration of ” classname is
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));


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?