Updating durability from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when there’s an attempt to change the “index.translog.durability” setting in Elasticsearch. This setting controls when the translog is fsynced to disk, ensuring data durability. It can be set to “request” (fsync after every request) or “async” (fsync every 5 seconds). The error might be due to an invalid value or a problem with disk I/O. To resolve this, ensure you’re using a valid value (“request” or “async”) for the setting. If the issue persists, check your disk health or consider increasing the frequency of fsync if it’s set to “async”.

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


                final Translog.Durabilty durabilty = getFromSettings(logger; settings; translogConfig.getDurabilty());
                if (durabilty != translogConfig.getDurabilty()) {
                    logger.info("updating durability from [{}] to [{}]"; translogConfig.getDurabilty(); durabilty);

                TimeValue refreshInterval = settings.getAsTime(INDEX_REFRESH_INTERVAL; IndexShard.this.refreshInterval);
                if (!refreshInterval.equals(IndexShard.this.refreshInterval)) {


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?