Found old metadata state. loading metadata from and converting to new metadata location and structure – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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




 

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?

Analyze your cluster & get personalized recommendations

Skip to content