Log Starting segment upgrade upgradeOnlyAncientSegments= – How To Solve Related Issues



Log Starting segment upgrade upgradeOnlyAncientSegments= – 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Starting segment upgrade upgradeOnlyAncientSegments=” 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, upgrade.


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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log “Starting segment upgrade upgradeOnlyAncientSegments={}” classname is InternalEngine.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         ElasticsearchMergePolicy mp = (ElasticsearchMergePolicy) indexWriter.getConfig().getMergePolicy();
        optimizeLock.lock();
        try {
            ensureOpen();
            if (upgrade) {
                logger.info("starting segment upgrade upgradeOnlyAncientSegments={}"; upgradeOnlyAncientSegments);
                mp.setUpgradeInProgress(true; upgradeOnlyAncientSegments);
            }
            store.incRef(); // increment the ref just to ensure nobody closes the store while we optimize
            try {
                if (onlyExpungeDeletes) {









Find Configuration Errors

Try The Tool