Updating indices.recovery.concurrent-small-file-streams from to – How to solve related issues

Updating indices.recovery.concurrent-small-file-streams 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.concurrent-small-file-streams from to ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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


            int concurrentSmallFileStreams = settings.getAsInt(INDICES_RECOVERY_CONCURRENT_SMALL_FILE_STREAMS; RecoverySettings.this.concurrentSmallFileStreams);
            if (concurrentSmallFileStreams != RecoverySettings.this.concurrentSmallFileStreams) {
                logger.info("updating [indices.recovery.concurrent_small_file_streams] from [{}] to [{}]"; RecoverySettings.this.concurrentSmallFileStreams; concurrentSmallFileStreams);
                RecoverySettings.this.concurrentSmallFileStreams = concurrentSmallFileStreams;

            RecoverySettings.this.retryDelayNetwork = maybeUpdate(RecoverySettings.this.retryDelayNetwork; settings; INDICES_RECOVERY_RETRY_DELAY_NETWORK);


Run the Check-Up to get a customized report like this:

Analyze your cluster