Updating disable flush 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 disable the flush operation in Elasticsearch. Disabling flush can lead to data loss and is generally not recommended. To resolve this issue, you can re-enable the flush operation by setting the ‘index.translog.flush_threshold_size’ to a reasonable value. Alternatively, you can also set ‘index.translog.durability’ to ‘async’ to allow Elasticsearch to decide when to perform the flush operation.

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

Log Context

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

                 logger.info("updating interval from [{}] to [{}]"; TranslogService.this.interval; interval);
                TranslogService.this.interval = interval;
            boolean disableFlush = settings.getAsBoolean(INDEX_TRANSLOG_DISABLE_FLUSH; TranslogService.this.disableFlush);
            if (disableFlush != TranslogService.this.disableFlush) {
                logger.info("updating disable_flush from [{}] to [{}]"; TranslogService.this.disableFlush; disableFlush);
                TranslogService.this.disableFlush = disableFlush;


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?