Has a wrong value ; defaulting to indices_all_active – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

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, cluster, rebalance and routing.

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);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content