Updating refresh interval from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when there is an attempt to update the refresh interval of an Elasticsearch index, but the new value is not specified or is invalid. The refresh interval controls how often updated data becomes searchable. To resolve this, ensure you’re providing a valid value for the refresh interval. It should be a positive integer followed by a time unit (like ‘5s’ for 5 seconds). If you want to disable refreshing, use ‘-1’. Also, check your permissions, as you need the ‘manage’ index privilege to change settings.

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

Log Context

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


                TimeValue refreshInterval = settings.getAsTime(INDEX_REFRESH_INTERVAL; IndexShard.this.refreshInterval);
                if (!refreshInterval.equals(IndexShard.this.refreshInterval)) {
                    logger.info("updating refresh_interval from [{}] to [{}]"; IndexShard.this.refreshInterval; refreshInterval);
                    if (refreshScheduledFuture != null) {
                        // NOTE: we pass false here so we do NOT attempt Thread.interrupt if EngineRefresher.run is currently running.
                        // This is
                        // very important; because doing so can cause files to suddenly be closed if they were doing IO when the interrupt
                        // hit.  See https://issues.apache.org/jira/browse/LUCENE-2239


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?