Opening indices – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is trying to open indices that were previously closed. This could be due to a manual command or an automated process. The error might be due to insufficient resources, incorrect permissions, or a network issue. To resolve this, ensure that the Elasticsearch cluster has enough resources, check the permissions for the indices, and verify the network connectivity. If the issue persists, consider checking the Elasticsearch logs for more detailed error messages.

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

Log Context

Log “opening indices [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        shardLimitValidator.validateShardLimit(currentState; indices);
        if (indicesToOpen.isEmpty()) {
            return currentState;
        } -> new ParameterizedMessage("opening indices [{}]";
            String.join(";"; -> (CharSequence) i.getIndex().toString())::iterator)));

        final Metadata.Builder metadata = Metadata.builder(currentState.metadata());
        final ClusterBlocks.Builder blocks = ClusterBlocks.builder().blocks(currentState.blocks());
        final Version minIndexCompatibilityVersion = currentState.getNodes().getMaxNodeVersion().minimumIndexCompatibilityVersion();