Updating indices.recovery.file-chunk-size 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 run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Updating indices.recovery.file-chunk-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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

                 }
            }

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

            int translogOps = settings.getAsInt(INDICES_RECOVERY_TRANSLOG_OPS; RecoverySettings.this.translogOps);
            if (translogOps != RecoverySettings.this.translogOps) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content