Adding block to indices – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

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 is trying to add a block to certain indices but encounters an issue. This could be due to insufficient permissions, a network issue, or a problem with the index itself. To resolve this, you could check the permissions of the user trying to add the block, ensure the network connection is stable, or investigate the health and status of the index. If the index is corrupted or locked, it may need to be repaired or unlocked.

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 ” adding block {} to indices {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: indices, cluster, metadata.

Log Context

Log “adding block {} to indices {}” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                    .settingsVersion(indexMetadata.getSettingsVersion() + 1));
        }"adding block {} to indices {}";;
        return Tuple.tuple(ClusterState.builder(currentState).blocks(blocks).metadata(metadata)
                .routingTable(; blockedIndices);


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