Log Now throttling indexing: numMergesInFlight=; maxNumMerges= – How To Solve Related Issues


Log Now 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 try running the 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 ” Now throttling indexing: numMergesInFlight=; maxNumMerges= ” 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.

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 “Now 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 beforeMerge(OnGoingMerge merge) {
            int maxNumMerges = mergeScheduler.getMaxMergeCount();
            if (numMergesInFlight.incrementAndGet() > maxNumMerges) {
                if (isThrottling.getAndSet(true) == false) {
                    logger.info("now throttling indexing: numMergesInFlight={}; maxNumMerges={}"; numMergesInFlight; maxNumMerges);
                    activateThrottling();
                }
            }
        }




 

Optimize Elasticsearch Performance

Try The Tool