Non-internal repository already registered this repository will block the – 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 has already been registered. This could be due to a configuration error or a script running multiple times. To resolve this issue, you can either delete the existing repository using the DELETE repository API before re-registering it, or check your scripts and configurations to ensure that the repository is not being registered multiple times. Also, ensure that the repository name is unique across all scripts and configurations to avoid conflicts.

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, repository.

Log Context

Log “non-internal repository [{}] already registered. this repository will block the ” classname is
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) {


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?