Metadata state not restored; reason: – How to solve related issues

Average Read Time

2 Mins

Metadata state not restored; reason: – How to solve related issues

Opster Team

Jan-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 ” Metadata state not restored; reason: ” 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 “Metadata state not restored; reason: {}” classname is GatewayService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         
Override
        public void onFailure(String message) {
            recovered.set(false);
            scheduledRecovery.set(false);
            // don't remove the block here; we don't want to allow anything in such a case
            logger.info("metadata state not restored; reason: {}"; message);
        }

    }

    // used for testing



 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content