Found old metadata state loading metadata from and converting to new metadata location and strucutre – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch detects old metadata state during the process of loading metadata. This could be due to an upgrade or migration where the new version of Elasticsearch uses a different metadata structure. To resolve this issue, you can allow Elasticsearch to automatically convert the old metadata to the new structure. Alternatively, you can manually migrate the metadata to the new structure before starting Elasticsearch. Lastly, ensure that all nodes in the cluster are running the same version of Elasticsearch to avoid inconsistencies.

This guide will help you check for common problems that cause the log ” found old metadata state; loading metadata from [{}] and converting to new metadata location and strucutre… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata.

Log Context

Log “found old metadata state; loading metadata from [{}] and converting to new metadata location and strucutre…” classname is LocalGatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
        if (metaData == null) {
            return;
        }

        logger.info("found old metadata state; loading metadata from [{}] and converting to new metadata location and strucutre..."; metaDataFile.getAbsolutePath());

        writeGlobalState("upgrade"; MetaData.builder(metaData).version(version).build(); null);
        for (IndexMetaData indexMetaData : metaData) {
            IndexMetaData.Builder indexMetaDataBuilder = IndexMetaData.builder(indexMetaData).version(version);
            // set the created version to 0.18

 

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?