Completed adding index blocks block to indices – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.5-8.9

Briefly, this error occurs when Elasticsearch successfully adds a block to an index or indices. This is not an error message, but an informational message indicating that a certain operation has been completed successfully. If you see this message, it means that the operation to add blocks to the index has been completed. If you didn’t intend to add blocks, you may need to review your Elasticsearch operations or scripts. To remove the blocks, you can use the “remove_index_blocks” API. Always ensure to backup your data before making any changes to your indices.

This guide will help you check for common problems that cause the log ” completed adding [index.blocks.{}] block to indices {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, cluster.

Log Context

Log “completed adding [index.blocks.{}] block to indices {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            } catch (final IndexNotFoundException e) {
                logger.debug("index {} has been deleted since blocking it started; ignoring"; index);
        }"completed adding [index.blocks.{}] block to indices {}";; effectivelyBlockedIndices);
        return Tuple.tuple(ClusterState.builder(currentState).blocks(blocks).build(); List.copyOf(blockingResults.values()));

     * @return Generates a {@link ClusterBlock} that blocks read and write operations on soon-to-be-closed indices. The