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

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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;




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content