Conversion to new metadata location and format done. backup create at – 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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Conversion to new metadata location and format done. backup create at ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata.

Log Context

Log “conversion to new metadata location and format done; backup create at [{}]” classname is LocalGatewayMetaState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 }
                stateFile.delete();
            }
        }

        logger.info("conversion to new metadata location and format done; backup create at [{}]"; backupFile.getAbsolutePath());
    }

    class RemoveDanglingIndex implements Runnable {

        private final IndexMetaData metaData;




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content