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

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 {
            type = CLUSTER_ROUTING_ALLOCATION_ALLOW_REBALANCE_SETTING.get(settings);
        } catch (IllegalStateException e) {
            logger.warn("[{}] has a wrong value {}; defaulting to 'indices_all_active'";
                    CLUSTER_ROUTING_ALLOCATION_ALLOW_REBALANCE_SETTING;
                    CLUSTER_ROUTING_ALLOCATION_ALLOW_REBALANCE_SETTING.getRaw(settings));
            type = ClusterRebalanceType.INDICES_ALL_ACTIVE;
        }
        logger.debug("using [{}] with [{}]"; CLUSTER_ROUTING_ALLOCATION_ALLOW_REBALANCE; type);




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster