Doesn’t match any of the locations specified by path.repo because this setting is empty – How to solve related issues

Doesn’t match any of the locations specified by path.repo because this setting is empty – How to solve related issues

Opster Team

Feb-21, Version: 1.7-8.0

It’s important to ensure your path repository setting is configured correctly to ensure location identification. Before you begin reading this guide, we recommend you run the Elasticsearch Error Check-Up to check your configuration and resolve issues such as the above.



This guide will help you check for common problems that cause the log “Doesn’t match any of the locations specified by path.repo because this setting is empty” 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.

Log Context

Log “The specified location [{}] should start with a repository path specified by” classname is FsRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 logger.warn("The specified location [{}] doesn't start with any "
                    + "repository paths specified by the path.repo setting: [{}] "; location; environment.repoFiles());
                throw new RepositoryException(metadata.name(); "location [" + location
                    + "] doesn't match any of the locations specified by path.repo");
            } else {
                logger.warn("The specified location [{}] should start with a repository path specified by"
                    + " the path.repo setting; but the path.repo setting was not set on this node"; location);
                throw new RepositoryException(metadata.name(); "location [" + location
                    + "] doesn't match any of the locations specified by path.repo because this setting is empty");
            }
        }




 

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

Analyze your cluster