Briefly, this error occurs when you’re trying to use Amazon S3’s Glacier storage class with Elasticsearch, which is not supported. Elasticsearch requires immediate access to data, but Glacier is designed for long-term archival storage with retrieval times that can take several hours. To resolve this issue, you can either change your S3 storage class to a class that provides immediate access, such as Standard, or configure a lifecycle policy to move data from Glacier to a supported class before Elasticsearch needs to access it.
This guide will help you check for common problems that cause the log ” Glacier storage class is not supported ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-s3, storage, 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 “Glacier storage class is not supported” class name is S3BlobStore.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} try {
final StorageClass _storageClass = StorageClass.fromValue(storageClass.toUpperCase(Locale.ENGLISH));
if (_storageClass.equals(StorageClass.Glacier)) {
throw new BlobStoreException("Glacier storage class is not supported");
} return _storageClass;
} catch (final IllegalArgumentException illegalArgumentException) {
throw new BlobStoreException("`" + storageClass + "` is not a valid S3 Storage Class.");
