Metadata state not restored reason – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch fails to restore the metadata state from a snapshot during a cluster recovery or migration process. This could be due to issues like corrupted snapshot files, insufficient permissions, or network connectivity problems. To resolve this, you can try the following: 1) Check and repair any corrupted snapshot files. 2) Ensure that Elasticsearch has the necessary permissions to access the snapshot files. 3) Verify your network connectivity. 4) If the issue persists, consider creating a new snapshot and restoring from that.

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
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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


    // used for testing