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

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: metadata.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

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




 

Run the Check-Up to get a customized report like this:

Analyze your cluster