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

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch detects old metadata state while loading metadata from and converting to a new metadata location and structure. This could be due to an upgrade or migration process. To resolve this issue, you can 1) Ensure that the Elasticsearch version you’re using is compatible with the metadata structure. 2) Check the integrity of your metadata files. 3) If the error persists, consider reindexing your data. Always remember to backup your data before performing these operations to prevent data loss.

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 structure… ” 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 structure…” 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 structure..."; metaDataFile.getAbsolutePath());

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

 

 [ratemypost]