Missing location – How to solve this Elasticsearch error

Missing location – How to solve this Elasticsearch error

Opster Team

July-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 ” missing location ” 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.

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”missing location”classname  is FsRepository.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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) {
  if (environment.repoFiles().length > 0) {
  logger.warn("The specified location [{}] doesn't start with any "


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

Analyze your cluster