Updating max_merge_count from to – How to solve related issues

Updating max_merge_count from to – 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 ” Updating max_merge_count from to ” 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

Log “updating [max_merge_count] from [{}] to [{}]” classname is ConcurrentMergeSchedulerProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            int maxMergeCount = settings.getAsInt("index.merge.scheduler.max_merge_count"; ConcurrentMergeSchedulerProvider.this.maxMergeCount);
            if (maxMergeCount != ConcurrentMergeSchedulerProvider.this.maxMergeCount) {
                logger.info("updating [max_merge_count] from [{}] to [{}]"; ConcurrentMergeSchedulerProvider.this.maxMergeCount; maxMergeCount);
                ConcurrentMergeSchedulerProvider.this.maxMergeCount = maxMergeCount;
                for (CustomConcurrentMergeScheduler scheduler : schedulers) {
                    scheduler.setMaxMergesAndThreads(maxMergeCount; ConcurrentMergeSchedulerProvider.this.maxThreadCount);


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

Analyze your cluster