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 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 ” 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.

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



 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content