Updated: Feb-20
Elasticsearch Version: 1.7-8.0Background
Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.
To troubleshoot log “Failed to finish repository verification” it’s important to understand a few problems related to Elasticsearch concepts repositories, repository-azure. See bellow important tips and explanations on these concepts
Repository in Elasticsearch
What it is
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read the Glossary term 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 per cluster can be created. 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 a repository of type fs:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}
Notes and common problems
- S3, HDFS , Azure and Google Cloud requires 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 in case you are planning to use repo type of file system otherwise it will fail
- In case of 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 in partial snapshots.
Log Context
Log”[{}] failed to finish repository verification” classname is RepositoriesService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
});
} catch (Throwable t) {
try {
repository.endVerification(verificationToken);
} catch (Throwable t1) {
logger.warn("[{}] failed to finish repository verification"; t1; repositoryName);
}
listener.onFailure(t);
}
} else {
listener.onResponse(new VerifyResponse(new DiscoveryNode[0]; new VerificationFailure[0]));
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
1 Curator Failed To Verify All Nodes
About Opster
Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance
