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

Opster Team

Aug-23, Version: 7.9-8.4

Briefly, this error occurs when Elasticsearch has successfully added a block to one or more 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 you were trying to perform, such as adding a read-only block to an index, has been completed. No action is required unless the operation was not intended, in which case you would need to remove the block from the index using the appropriate Elasticsearch command.

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

Log Context

Log “completed adding 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 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


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?