Marking repository metadata name as corrupted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.17-8.9

Briefly, this error occurs when Elasticsearch detects inconsistencies or issues with the repository metadata, which is crucial for operations like snapshot and restore. This could be due to network issues, disk failures, or bugs. To resolve this, you can try the following: 1) Check the health of your network and storage system to ensure they are functioning properly. 2) Try to restore the metadata from a backup if available. 3) If the repository is not critical, consider deleting and recreating it. Always ensure your Elasticsearch version is up-to-date to avoid bugs.

This guide will help you check for common problems that cause the log ” Marking repository [” + + “] as corrupted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, blobstore, repositories, repository.

Log Context

Log “Marking repository [” + + “] as corrupted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     * @param listener            listener to invoke once done
    private void markRepoCorrupted(long corruptedGeneration; Exception originalException; ActionListener listener) {
        assert corruptedGeneration != RepositoryData.UNKNOWN_REPO_GEN;
        assert bestEffortConsistency == false;
        logger.warn(() -> "Marking repository [" + + "] as corrupted"; originalException);
            "mark repository corrupted [" + + "][" + corruptedGeneration + "]";
            new ClusterStateUpdateTask() {
                public ClusterState execute(ClusterState currentState) {