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

Opster Team

Aug-23, Version: 2.3-2.3

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, high load on the nodes, or a misconfiguration. To resolve this issue, you can increase the timeout setting, optimize your cluster to handle the load better, or check your network configuration to ensure there are no connectivity issues. Additionally, ensure that your Elasticsearch nodes have sufficient resources (CPU, memory, disk I/O) to operate efficiently.

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

Log Context

Log “NodeStatsAction timed out for ClusterInfoUpdateJob (reason [{}])” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            public void onFailure(Throwable e) {
                if (e instanceof ReceiveTimeoutTransportException) {
                    logger.error("NodeStatsAction timed out for ClusterInfoUpdateJob (reason [{}])"; e.getMessage());
                } else {
                    if (e instanceof ClusterBlockException) {
                        if (logger.isTraceEnabled()) {
                            logger.trace("Failed to execute NodeStatsAction 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?