Briefly, this error occurs when Elasticsearch tries to archive repository statistics but fails because the allocated storage space is full. This could be due to a large amount of data or insufficient storage space. To resolve this issue, you can either increase the storage space or delete unnecessary data. Regularly monitoring and managing your storage can prevent this issue in the future. Also, consider implementing a data retention policy to automatically delete old data.
This guide will help you check for common problems that cause the log ” Unable to archive the repository stats [{}] as the archive is full. ” 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 “Unable to archive the repository stats [{}] as the archive is full.” classname is RepositoriesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
private void archiveRepositoryStats(Repository repository; long clusterStateVersion) { if (repository instanceof MeteredBlobStoreRepository) { RepositoryStatsSnapshot stats = ((MeteredBlobStoreRepository) repository).statsSnapshotForArchival(clusterStateVersion); if (repositoriesStatsArchive.archive(stats) == false) { logger.warn("Unable to archive the repository stats [{}] as the archive is full."; stats); } } } /**