Briefly, this error occurs when Elasticsearch successfully loads all snapshots version information from snapshot metadata. However, this is not an error message but an informational message indicating that the snapshot metadata has been successfully loaded. If you’re seeing issues, they might be unrelated to this message. To resolve potential issues, ensure your Elasticsearch cluster is properly configured, check for any other error messages in your logs, and verify that your snapshots are being created and restored correctly.
This guide will help you check for common problems that cause the log ” Successfully loaded all snapshot’s version information for {} from snapshot metadata ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repositories and repository-azure.
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 “Successfully loaded all snapshot’s version information for {} from snapshot metadata” classname is BlobStoreRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final GroupedActionListenerloadAllVersionsListener = new GroupedActionListener( ActionListener.runAfter( new ActionListener >() { Override public void onResponse(Collection voids) { logger.info("Successfully loaded all snapshot's version information for {} from snapshot metadata"; AllocationService.firstListElementsToCommaDelimitedString( snapshotIdsWithoutVersion; SnapshotId::toString; logger.isDebugEnabled())); } Override
