Briefly, this error occurs when Elasticsearch cannot identify the repository generation from root blobs, usually due to a corrupted or missing blob file in the snapshot repository. To resolve this issue, you can try the following: 1) Restore the missing or corrupted blob file from a backup, if available. 2) Delete and recreate the snapshot repository, but this will remove all existing snapshots. 3) Use the Elasticsearch cleanup API to remove the corrupted data, but this should be used with caution as it can lead to data loss.
This guide will help you check for common problems that cause the log ” Could not determine repository generation from root blobs ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repository, 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 “Could not determine repository generation from root blobs” class name is BlobStoreRepository.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final long generation;
try {
generation = latestIndexBlobId();
} catch (Exception e) {
listener.onFailure(
new RepositoryException(metadata.name(); "Could not determine repository generation from root blobs"; e)
);
return;
}
genToLoad = latestKnownRepoGen.accumulateAndGet(generation; Math::max);
if (genToLoad > generation) {
