Updating indices recovery translog size from to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is recovering an index and updating the transaction log (translog) size. This usually happens after a node failure or during a shard relocation. The translog plays a crucial role in operation durability, hence any issues with it can affect the stability of your Elasticsearch. To resolve this, you can consider increasing the translog size limit, ensure enough disk space is available, or check the health of your nodes and network. Also, regularly monitor your Elasticsearch cluster to prevent such issues.

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

Log Context

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

                 RecoverySettings.this.translogOps = translogOps;

            ByteSizeValue translogSize = settings.getAsBytesSize(INDICES_RECOVERY_TRANSLOG_SIZE; RecoverySettings.this.translogSize);
            if (!translogSize.equals(RecoverySettings.this.translogSize)) {
                logger.info("updating [indices.recovery.translog_size] from [{}] to [{}]"; RecoverySettings.this.translogSize; translogSize);
                RecoverySettings.this.translogSize = translogSize;

            boolean compress = settings.getAsBoolean(INDICES_RECOVERY_COMPRESS; RecoverySettings.this.compress);
            if (compress != RecoverySettings.this.compress) {