Update repository – How to solve related issues

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

                        if (!found) {
                            logger.info("put repository [{}]"; request.name);
                            repositoriesMetaData.add(new RepositoryMetaData(request.name; request.type; request.settings));
                        } else {
                            logger.info("update repository [{}]"; request.name);
                        repositories = new RepositoriesMetaData(repositoriesMetaData);
                    mdBuilder.putCustom(RepositoriesMetaData.TYPE; repositories);
                    return ClusterState.builder(currentState).metaData(mdBuilder).build();


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

Analyze your cluster