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

                     ensureRepositoryNotInUse(currentState; request.name);
                    MetaData metaData = currentState.metaData();
                    MetaData.Builder mdBuilder = MetaData.builder(currentState.metaData());
                    RepositoriesMetaData repositories = metaData.custom(RepositoriesMetaData.TYPE);
                    if (repositories == null) {
                        logger.info("put repository [{}]"; request.name);
                        repositories = new RepositoriesMetaData(
                            Collections.singletonList(new RepositoryMetaData(request.name; request.type; request.settings)));
                    } else {
                        boolean found = false;
                        List repositoriesMetaData = new ArrayList(repositories.repositories().size() + 1);


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content