Briefly, this error occurs when Elasticsearch is unable to parse the URL provided. This could be due to an incorrect URL format, a typo, or the URL might be unreachable. To resolve this issue, first, verify the URL format and ensure it’s correct. Second, check for any typographical errors in the URL. Lastly, ensure the URL is accessible and the server it points to is up and running.
This guide will help you check for common problems that cause the log ” cannot parse the specified url [” + urlToCheck + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories.
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 “cannot parse the specified url [” + urlToCheck + “]” class name is URLRepository.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// URL matches white list - no additional processing is needed
return urlToCheck;
}
} catch (URISyntaxException ex) {
logger.warn("cannot parse the specified url [{}]"; urlToCheck);
throw new RepositoryException(getMetadata().name(); "cannot parse the specified url [" + urlToCheck + "]");
}
// We didn't match white list - try to resolve against path.repo
URL normalizedUrl = environment.resolveRepoURL(urlToCheck);
if (normalizedUrl == null) {
String logMessage = "The specified url [{}] doesn't start with any repository paths specified by the "
