Log Updating index.compound-format from to – How To Solve Related Issues



Log Updating index.compound-format from to – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Updating index.compound-format from to ” 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, merge and shard.

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. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “updating index.compound_format from [{}] to [{}]” classname is MergePolicyConfig.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             mergePolicy.setReclaimDeletesWeight(reclaimDeletesWeight);
        }

        double noCFSRatio = parseNoCFSRatio(settings.get(INDEX_COMPOUND_FORMAT; Double.toString(MergePolicyConfig.this.noCFSRatio)));
        if (noCFSRatio != MergePolicyConfig.this.noCFSRatio) {
            logger.info("updating index.compound_format from [{}] to [{}]"; formatNoCFSRatio(MergePolicyConfig.this.noCFSRatio); formatNoCFSRatio(noCFSRatio));
            mergePolicy.setNoCFSRatio(noCFSRatio);
            MergePolicyConfig.this.noCFSRatio = noCFSRatio;
        }
    }







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 Github Issue Number 10778

2 Github Issue Number 6409






Optimize Elasticsearch Performance

Try The Tool