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

Opster Team

Aug-23, Version: 6.8-7.11

Briefly, this error occurs when the Elasticsearch cluster is unable to gather statistics about the nodes within the specified timeout period. This could be due to network issues, overloaded nodes, or a misconfigured cluster. To resolve this issue, you can increase the timeout settings, optimize your cluster to reduce load, or check your network connectivity to ensure all nodes are reachable. Additionally, ensure your cluster is properly configured and all nodes are functioning correctly.

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

Log Context

Log “NodeStatsAction 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("NodeStatsAction timed out for ClusterInfoUpdateJob"; e);
                } else {
                    if (e instanceof ClusterBlockException) {
                        if (logger.isTraceEnabled()) {
                            logger.trace("Failed to execute NodeStatsAction for ClusterInfoUpdateJob"; e);