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 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 ” Starting segment upgrade upgradeOnlyAncientSegments= ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and upgrade.

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 “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) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content