Put repository – How To Solve Related Issues

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 try running the 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. 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 “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);




 

Optimize Elasticsearch Performance

Try The Tool