Stop throttling indexing: numMergesInFlight=; maxNumMerges= – How to solve related issues

Opster Team

Jan-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 ” Stop throttling indexing: numMergesInFlight=; maxNumMerges= ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Stop throttling indexing: numMergesInFlight={}; maxNumMerges={}” classname is InternalEngine.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         
Override
        public synchronized void afterMerge(OnGoingMerge merge) {
            int maxNumMerges = mergeScheduler.getMaxMergeCount();
            if (numMergesInFlight.decrementAndGet() 

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content