Failed to read global metadata – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to read the global metadata, which is crucial for its operations. This could be due to issues like corruption of metadata, insufficient permissions, or disk space issues. To resolve this, you can try restoring from a backup, checking and fixing disk space issues, or adjusting the permissions to ensure Elasticsearch has the necessary access. If the metadata is corrupted, you may need to rebuild the index.

This guide will help you check for common problems that cause the log ” failed to read global metadata ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, metadata, repositories.

Log Context

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

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


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?