Briefly, this error occurs when Elasticsearch is unable to verify the repository, often due to incorrect configuration or connectivity issues. To resolve this, ensure that the repository is correctly configured and accessible. Check the repository’s URL, credentials, and permissions. If it’s a remote repository, verify network connectivity. If it’s a snapshot repository, ensure it’s properly set up and the path.data directory is accessible. Also, check Elasticsearch logs for more detailed error information.
This guide will help you check for common problems that cause the log ” [” + repository + “] failed to verify repository ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository.
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 “[” + repository + “] failed to verify repository” classname is VerifyNodeRepositoryAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
for (final DiscoveryNode node : nodes) {
if (node.equals(localNode)) {
try {
doVerify(repository; verificationToken; localNode);
} catch (Exception e) {
logger.warn(() -> "[" + repository + "] failed to verify repository"; e);
errors.add(new VerificationFailure(node.getId(); e));
}
if (counter.decrementAndGet() == 0) {
finishVerification(repository; listener; nodes; errors);
}
