Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

This guide will help you check for common problems that cause the log “Failed to reassign persistent tasks” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, persistent.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

## enable shard routing
PUT /_cluster/settings
{
    "persistent" : {
        "cluster.routing.allocation.enable" : "all"
    }
}
## enable rebalancing of shards
PUT /_cluster/settings
{
    "persistent" : {
        "cluster.routing.rebalance.enable" : "all"
    }
}
## limit the heap size for fielddata
PUT /_cluster/settings
{
    "persistent" : {
                 “indices.breaker.fielddata.limit”: "30%"
    }
}

                 return reassignTasks(currentState);
            }

            
Override
            public void onFailure(String source; Exception e) {
                logger.warn("failed to reassign persistent tasks"; e);
                // There must be a task that's worth rechecking because there was one
                // that caused this method to be called and the method failed to assign it
                periodicRechecker.rescheduleIfNecessary();
            }

Find Configuration Errors

Analyze Now