Updating max_thread_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 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 ” Updating max_thread_count from to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and merge.

Log Context

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

     class ApplySettings implements IndexSettingsService.Listener {
        public void onRefreshSettings(Settings settings) {
            int maxThreadCount = settings.getAsInt("index.merge.scheduler.max_thread_count"; ConcurrentMergeSchedulerProvider.this.maxThreadCount);
            if (maxThreadCount != ConcurrentMergeSchedulerProvider.this.maxThreadCount) {
                logger.info("updating [max_thread_count] from [{}] to [{}]"; ConcurrentMergeSchedulerProvider.this.maxThreadCount; maxThreadCount);
                ConcurrentMergeSchedulerProvider.this.maxThreadCount = maxThreadCount;
                for (CustomConcurrentMergeScheduler scheduler : schedulers) {
                    scheduler.setMaxMergesAndThreads(ConcurrentMergeSchedulerProvider.this.maxMergeCount; maxThreadCount);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content