Unable to delete global metadata file – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch is unable to delete a global metadata file due to insufficient permissions, a locked file, or a disk space issue. To resolve this, you can try the following: 1) Check and modify the file permissions to ensure Elasticsearch has the necessary access. 2) Ensure the file isn’t being used by another process. 3) Check if there’s enough disk space and free up space if necessary. Always ensure to back up your data before making any changes.

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

Log Context

Log “[{}] Unable to delete global metadata file [{}]” classname is BlobStoreRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private void deleteGlobalMetaDataBlobIgnoringErrors(final SnapshotInfo snapshotInfo; final String blobId) {
        try {
            globalMetaDataFormat.delete(blobContainer(); blobId);
        } catch (IOException e) {
            if (snapshotInfo != null) {
                logger.warn(() -> new ParameterizedMessage("[{}] Unable to delete global metadata file [{}]";
                    snapshotInfo.snapshotId(); blobId); e);
            } else {
                logger.warn(() -> new ParameterizedMessage("Unable to delete global metadata file [{}]"; blobId); e);


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?