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

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

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Stop throttling indexing: numMergesInFlight=; maxNumMerges=” it’s important to understand a few problems related to Elasticsearch concepts index. See bellow important tips and explanations on these concepts

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() < maxNumMerges) {
                if (isThrottling.getAndSet(false)) {
                    logger.info("stop throttling indexing: numMergesInFlight={}; maxNumMerges={}";
                        numMergesInFlight; maxNumMerges);
                    deactivateThrottling();
                }
            }
            if (indexWriter.hasPendingMerges() == false &&



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How to prevent Elasticsearch from index throttling? 7.98 K 5

Now Throttling Indexing  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now