The repository location is missing; it should point to a shared file system location that is available on all master and data nodes – How to solve related issues

Opster Team

Feb-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 that is available on all master and data nodes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file, master, 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 that is available on all master and data nodes” classname is FsRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public FsRepository(RepositoryName name; RepositorySettings repositorySettings; IndexShardRepository indexShardRepository; Environment environment) throws IOException {
        super(name.getName(); repositorySettings; indexShardRepository);
        Path locationFile;
        String location = repositorySettings.settings().get("location"; settings.get("repositories.fs.location"));
        if (location == null) {
            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(name.name(); "missing location");
        }
        locationFile = environment.resolveRepoFile(location);
        if (locationFile == null) {
            if (environment.repoFiles().length > 0) {




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content