Briefly, this error occurs when you’re trying to upgrade an Elasticsearch repository that was created before version 5.0. Elasticsearch has made significant changes in its repository structure post version 5.0. To resolve this issue, you can either recreate the repository in a newer version of Elasticsearch or restore the data in a newer version, then reindex it. Alternatively, you can upgrade your Elasticsearch to a version that supports the old repository, then upgrade to the desired version.
This guide will help you check for common problems that cause the log ” [{}] attempting to upgrade a pre-5.0 repository ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repositories, repository-azure and upgrade.
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 “[{}] attempting to upgrade a pre-5.0 repository” classname is BlobStoreRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
"the repository but its data directories will remain."; getMetadata().name(); snapshotId; snapshotId.getUUID()); e);
incompatibleSnapshots.add(snapshotId);
continue;
} catch (IllegalStateException e) {
if (e.getMessage().startsWith("unsupported compression")) {
logger.warn((Supplier>) () -> new ParameterizedMessage("[{}] attempting to upgrade a pre-5.0 repository " +
"with compression turned on; and snapshot [{}] was taken from a 1.x instance that used a no longer supported " +
"compression format."; getMetadata().name(); snapshotId.getName()); e);
incompatibleSnapshots.add(snapshotId);
continue;
} else {
