The repository location is missing; it should point to a shared file system location – 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 ” The repository location is missing; it should point to a shared file system location ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file, 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 “The repository location is missing; it should point to a shared file system location” classname is FsRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         NamedXContentRegistry namedXContentRegistry) {
        super(metadata; environment.settings(); namedXContentRegistry);
        this.environment = environment;
        String location = REPOSITORIES_LOCATION_SETTING.get(metadata.settings());
        if (location.isEmpty()) {
            logger.warn("the repository location is missing; it should point to a shared file system location"
                + " that is available on all master and data nodes");
            throw new RepositoryException(metadata.name(); "missing location");
        }
        Path locationFile = environment.resolveRepoFile(location);
        if (locationFile == null) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content