allocator has been removed in 2.0 using instead – How to solve related issues

Opster Team

Feb-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.

This guide will help you check for common problems that cause the log ” allocator has been removed in 2.0 using instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “{} allocator has been removed in 2.0 using {} instead” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // bind ShardsAllocator
        String shardsAllocatorType = shardsAllocators.bindType(binder(); settings; ClusterModule.SHARDS_ALLOCATOR_TYPE_KEY; ClusterModule.BALANCED_ALLOCATOR);
        if (shardsAllocatorType.equals(ClusterModule.EVEN_SHARD_COUNT_ALLOCATOR)) {
            final ESLogger logger = Loggers.getLogger(getClass(); settings);
            logger.warn("{} allocator has been removed in 2.0 using {} instead"; ClusterModule.EVEN_SHARD_COUNT_ALLOCATOR; ClusterModule.BALANCED_ALLOCATOR);



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content