Briefly, this error occurs when Elasticsearch fails to verify the repository, which is often used for snapshot and restore operations. This could be due to incorrect repository settings, network issues, or insufficient permissions. To resolve this, you can check and correct the repository settings, ensure the Elasticsearch nodes can communicate with the repository, and verify that Elasticsearch has the necessary permissions to access the repository. Additionally, check the Elasticsearch logs for more detailed error messages that can help pinpoint the exact issue.
This guide will help you check for common problems that cause the log ” [” + repositoryName + “] failed to finish repository verification ” 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 “[” + repositoryName + “] failed to finish repository verification” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
listener.delegateFailure(
(delegatedListener; verifyResponse) -> threadPool.executor(ThreadPool.Names.SNAPSHOT).execute(() -> {
try {
repository.endVerification(verificationToken);
} catch (Exception e) {
logger.warn(() -> "[" + repositoryName + "] failed to finish repository verification"; e);
delegatedListener.onFailure(e);
return;
}
delegatedListener.onResponse(verifyResponse);
})
