Log Updating segments-per-tier from to – How To Solve Related Issues

Log Updating segments-per-tier from to – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Updating segments-per-tier 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, 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 discover the cause of many errors and provides suitable actionable recommendations. 

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);

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


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 Understanding Segments in Elasticsearch -views 20.52 K ,score 41

Tuning For High Update And Delete R  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now