Has a wrong value defaulting to indices all active – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.4

Briefly, this error occurs when Elasticsearch is unable to identify the specific index to perform operations on, and thus defaults to all active indices. This could be due to incorrect configuration or missing index name in the request. To resolve this, ensure that the correct index name is specified in your request. Also, check your Elasticsearch configuration to ensure that the default index is correctly set. If you’re using an API, ensure that the index parameter is correctly passed. Lastly, ensure that the index you’re trying to access actually exists in your Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” [{}] has a wrong value {}; defaulting to ‘indices_all_active’ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: allocation, routing, cluster.

Log Context

Log “[{}] has a wrong value {}; defaulting to ‘indices_all_active'” classname is ClusterRebalanceAllocationDecider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public ClusterRebalanceAllocationDecider(Settings settings; ClusterSettings clusterSettings) {
        try {
        } catch (IllegalStateException e) {
            logger.warn("[{}] has a wrong value {}; defaulting to 'indices_all_active'";
            type = ClusterRebalanceType.INDICES_ALL_ACTIVE;
        logger.debug("using [{}] with [{}]"; CLUSTER_ROUTING_ALLOCATION_ALLOW_REBALANCE; type);


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?