Updating calibrate size by deletes from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch is trying to adjust the size of an index by deleting documents. This could be due to a high number of deleted documents, causing the index to become too large. To resolve this issue, you can consider the following options: 1) Regularly optimize your index to purge deleted documents. 2) Increase the size of your Elasticsearch cluster to handle larger indices. 3) Implement a more efficient data retention policy to reduce the number of deletes. 4) Consider using the “update” API instead of “delete” and “index” for changing existing documents.

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

Log Context

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


            boolean oldCalibrateSizeByDeletes = mergePolicy.getCalibrateSizeByDeletes();
            boolean calibrateSizeByDeletes = settings.getAsBoolean(INDEX_MERGE_POLICY_CALIBRATE_SIZE_BY_DELETES; oldCalibrateSizeByDeletes);
            if (calibrateSizeByDeletes != oldCalibrateSizeByDeletes) {
                logger.info("updating calibrate_size_by_deletes from [{}] to [{}]"; oldCalibrateSizeByDeletes; calibrateSizeByDeletes);

            double noCFSRatio = parseNoCFSRatio(settings.get(INDEX_COMPOUND_FORMAT; Double.toString(LogDocMergePolicyProvider.this.noCFSRatio)));
            if (noCFSRatio != LogDocMergePolicyProvider.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?