Updating floor segment from mb 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 floor segment, which is the smallest unit of the index, from megabytes to another unit. This could be due to a configuration issue or a problem with the underlying storage system. To resolve this issue, you can check the Elasticsearch configuration for any errors, ensure that the storage system is functioning correctly, or try to rebuild the index. If the problem persists, you may need to consider increasing the size of the floor segment or reducing the size of the data being indexed.

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


        final double oldFloorSegmentMB = mergePolicy.getFloorSegmentMB();
        final ByteSizeValue floorSegment = settings.getAsBytesSize(INDEX_MERGE_POLICY_FLOOR_SEGMENT; null);
        if (floorSegment != null && floorSegment.mbFrac() != oldFloorSegmentMB) {
            logger.info("updating [floor_segment] from [{}mb] to [{}]"; oldFloorSegmentMB; floorSegment);

        final double oldSegmentsPerTier = mergePolicy.getSegmentsPerTier();
        final double segmentsPerTier = settings.getAsDouble(INDEX_MERGE_POLICY_SEGMENTS_PER_TIER; oldSegmentsPerTier);


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?