Updating fetch timeout 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Updating fetch timeout from to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

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


            TimeValue newFetchTimeout = settings.getAsTime(INTERNAL_CLUSTER_INFO_TIMEOUT; null);
            if (newFetchTimeout != null) {
                logger.info("updating fetch timeout [{}] from [{}] to [{}]"; INTERNAL_CLUSTER_INFO_TIMEOUT; fetchTimeout; newFetchTimeout);
                InternalClusterInfoService.this.fetchTimeout = newFetchTimeout;

            // We don't log about enabling it here; because the DiskThresholdDecider will already be logging about enable/disable


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content