Failed to delete metadata for index – How to solve related issues

Failed to delete metadata for index – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to delete metadata for index ” 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: blobstore, delete, index, metadata and repositories.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

         final SnapshotId snapshotId = snapshotInfo.snapshotId();
        BlobContainer indexMetaDataBlobContainer = blobStore().blobContainer(basePath().add("indices").add(indexId.getId()));
        try {
            indexMetaDataFormat.delete(indexMetaDataBlobContainer; snapshotId.getUUID());
        } catch (IOException ex) {
            logger.warn(() -> new ParameterizedMessage("[{}] failed to delete metadata for index [{}]";
                snapshotId; indexId.getName()); ex);
        }
    }

    /**




 

Run the Check-Up to get a customized report like this:

Analyze your cluster