Updating segments per tier from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is trying to update the number of segments per tier during the process of segment merging, but it encounters an issue. This could be due to incorrect configurations or insufficient resources. To resolve this, you can try the following: 1) Check and correct your Elasticsearch configurations related to segment merging. 2) Ensure that your Elasticsearch cluster has enough resources (CPU, memory, disk space) to perform the operation. 3) If the problem persists, consider upgrading your Elasticsearch version as it could be a bug in the current version.

This guide will help you check for common problems that cause the log ” updating [segments_per_tier] 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 [segments_per_tier] from [{}] to [{}]” classname is MergePolicyConfig.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         }

        final double oldSegmentsPerTier = mergePolicy.getSegmentsPerTier();
        final double segmentsPerTier = settings.getAsDouble(INDEX_MERGE_POLICY_SEGMENTS_PER_TIER; oldSegmentsPerTier);
        if (segmentsPerTier != oldSegmentsPerTier) {
            logger.info("updating [segments_per_tier] from [{}] to [{}]"; oldSegmentsPerTier; segmentsPerTier);
            mergePolicy.setSegmentsPerTier(segmentsPerTier);
        }

        final int oldMaxMergeAtOnce = mergePolicy.getMaxMergeAtOnce();
        int maxMergeAtOnce = settings.getAsInt(INDEX_MERGE_POLICY_MAX_MERGE_AT_ONCE; oldMaxMergeAtOnce);




 

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?