Ignoring index.merge.scheduler.max_merge_at_once . because we are using ConcurrentMergeScheduler(2. 1) – How to solve related issues

Average Read Time

2 Mins

Ignoring index.merge.scheduler.max_merge_at_once . because we are using ConcurrentMergeScheduler(2. 1) – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Ignoring index.merge.scheduler.max_merge_at_once . because we are using ConcurrentMergeScheduler(2. 1) ” 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: index and merge.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “ignoring index.merge.scheduler.max_merge_at_once [{}]; because we are using ConcurrentMergeScheduler(2; 1)” classname is SerialMergeSchedulerProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     
Inject
    public SerialMergeSchedulerProvider(ShardId shardId; 
IndexSettings Settings indexSettings; ThreadPool threadPool) {
        super(shardId; indexSettings; threadPool);
        Integer value = componentSettings.getAsInt("max_merge_at_once"; null);
        if (value != null) {
            logger.warn("ignoring index.merge.scheduler.max_merge_at_once [{}]; because we are using ConcurrentMergeScheduler(2; 1)"; value);
        }
        logger.trace("using [concurrent] merge scheduler; max_thread_count=1; max_merge_count=2");
    }

    
Override

 

Run the Check-Up to get a customized report like this:

Analyze your cluster