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

Opster Team

Aug-23, Version: 7.2-7.4

Briefly, this error occurs when Elasticsearch is unable to delete global metadata files due to insufficient permissions, disk space issues, or a file lock. To resolve this, you can try the following: 1) Check and adjust the permissions of the Elasticsearch directory to ensure it has write access. 2) Free up disk space if it’s running low. 3) Check for any processes that may be locking the file and terminate them. Always ensure to backup your data before making any changes to avoid data loss.

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

Log Context

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

            final List snapMetaFilesToDelete =
                Arrays.asList(snapshotFormat.blobName(snapshotId.getUUID()); globalMetaDataFormat.blobName(snapshotId.getUUID()));
            try {
            } catch (IOException e) {
                logger.warn(() -> new ParameterizedMessage("[{}] Unable to delete global metadata files"; snapshotId); e);
            final Map survivingIndices = updatedRepositoryData.getIndices();


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?