Attempting to upgrade a pre-5.0 repository – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 5.5-5.5

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.

Log Context

Log “[{}] attempting to upgrade a pre-5.0 repository” classname is
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);
            } 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);
                } else {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?