Updating reclaim deletes weight from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch tries to update the “reclaim deletes weight” parameter, which is used to control the priority of deleting documents that have been marked as deleted. This could be due to an incorrect configuration or a bug in the system. To resolve this issue, you can try to reset the parameter to its default value, ensure that your Elasticsearch version is up-to-date, or check your system for any bugs or issues that might be causing this error.

This guide will help you check for common problems that cause the log ” updating [reclaim_deletes_weight] from [{}] to [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, merge and shard.

Log Context

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


        final double oldReclaimDeletesWeight = mergePolicy.getReclaimDeletesWeight();
        final double reclaimDeletesWeight = settings.getAsDouble(INDEX_MERGE_POLICY_RECLAIM_DELETES_WEIGHT; oldReclaimDeletesWeight);
        if (reclaimDeletesWeight != oldReclaimDeletesWeight) {
            logger.info("updating [reclaim_deletes_weight] from [{}] to [{}]"; oldReclaimDeletesWeight; reclaimDeletesWeight);

        double noCFSRatio = parseNoCFSRatio(settings.get(INDEX_COMPOUND_FORMAT; Double.toString(MergePolicyConfig.this.noCFSRatio)));
        if (noCFSRatio != MergePolicyConfig.this.noCFSRatio) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?