Briefly, this error occurs when Elasticsearch tries to access a repository that is not defined in the path.repo setting. This could be due to a misconfiguration or a typo in the repository URL. To resolve this issue, you can either add the correct repository path to the path.repo setting in the Elasticsearch configuration file or correct the repository URL if it’s incorrect. Also, ensure that Elasticsearch has the necessary permissions to access the repository.
This guide will help you check for common problems that cause the log ” The specified url [{}] doesn’t start with any repository paths specified by the path.repo setting or by {} setting: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories and repository-azure.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “The specified url [{}] doesn’t start with any repository paths specified by the path.repo setting or by {} setting: [{}]” classname is URLRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
throw new RepositoryException(getMetadata().name(); "cannot parse the specified url [" + url + "]");
}
// We didn't match white list - try to resolve against path.repo
URL normalizedUrl = environment.resolveRepoURL(url);
if (normalizedUrl == null) {
logger.warn("The specified url [{}] doesn't start with any repository paths specified by the path.repo setting or by {} setting: [{}] "; url; ALLOWED_URLS_SETTING.getKey(); environment.repoFiles());
throw new RepositoryException(getMetadata().name(); "file url [" + url + "] doesn't match any of the locations specified by path.repo or " + ALLOWED_URLS_SETTING.getKey());
}
return normalizedUrl;
}
}
