Failed to read global metadata – Elasticsearch Error How To Solve Related Issues

Failed to read global metadata – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “failed to read global metadata” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, metadata, blobstore.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”failed to read global metadata”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
  return; snapshotId.getUUID());
  } catch (NoSuchFileException ex) {
  throw new SnapshotMissingException(; snapshotId; ex);
  } catch (IOException ex) {
  throw new SnapshotException(; snapshotId; "failed to read global metadata"; ex);
  public IndexMetadata getSnapshotIndexMetaData(RepositoryData repositoryData; SnapshotId snapshotId; IndexId index) throws IOException {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch crashes after showing t: failed to read local state , exiting -views 3,786 ,score 3

“Failed to read or upgrade local state, exiting…” when starting ES …  

Find Configuration Errors

Analyze Now