IndicesStatsAction timed out for ClusterInfoUpdateJob – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.11

Briefly, this error occurs when Elasticsearch’s IndicesStatsAction, a process that collects index statistics, takes longer than the set timeout period. This is often due to heavy load, insufficient resources, or network issues. To resolve this, you can increase the timeout setting, optimize your queries to reduce load, add more resources (like CPU, RAM, or storage), or troubleshoot potential network issues. Additionally, consider checking for any hardware failures or bottlenecks in your Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” IndicesStatsAction timed out for ClusterInfoUpdateJob ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, indices.

Log Context

Log “IndicesStatsAction timed out for ClusterInfoUpdateJob” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            public void onFailure(Exception e) {
                if (e instanceof ReceiveTimeoutTransportException) {
                    logger.error("IndicesStatsAction timed out for ClusterInfoUpdateJob"; e);
                } else {
                    if (e instanceof ClusterBlockException) {
                        if (logger.isTraceEnabled()) {
                            logger.trace("Failed to execute IndicesStatsAction for ClusterInfoUpdateJob"; e);


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?