How To Solve Issues Related to Log – Has a wrong value ; defaulting to indices_all_active

How To Solve Issues Related to Log – Has a wrong value ; defaulting to indices_all_active

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “Has a wrong value ; defaulting to indices_all_active” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, rebalance, routing. See bellow important tips and explanations on these concepts

Log Context

Log”[{}] has a wrong value {}; defaulting to ‘indices_all_active'” classname is
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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Avoid Rebalancing Upon Failure  

Github Issue Number 30162  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now