Glacier storage class is not supported – Elasticsearch Error How To Solve Related Issues

Glacier storage class is not supported – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Glacier storage class is not supported ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, storage, repository-s3 and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Glacier storage class is not supported”classname  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.");

 

Optimize Elasticsearch Performance

Try The Tool