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

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch adds a block to an index or multiple indices. This is not necessarily an error, but more of an informational message indicating a successful operation. However, if this operation was not intended, it could lead to issues. To resolve this, you can remove the block from the index using the “removeIndexBlock” API. If the block was added unintentionally, check your OpenSearch configurations and scripts to prevent this from happening in the future. Also, ensure that your OpenSearch cluster has proper access controls to prevent unauthorized operations.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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 OpenSearch concepts: cluster, indices, metadata.

Log Context

Log “completed adding block {} to indices {}” classname is
We extracted the following from OpenSearch 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(


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?

Get expert answers on Elasticsearch/OpenSearch