NodeStatsAction timed out for ClusterInfoUpdateJob – How to solve related issues

NodeStatsAction timed out for ClusterInfoUpdateJob – How to solve related issues

Opster Team

Jan-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 ” NodeStatsAction timed out for ClusterInfoUpdateJob ” 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: cluster and node.

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 “NodeStatsAction timed out for ClusterInfoUpdateJob” classname is InternalClusterInfoService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }

            
Override
            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);
                        }



 

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

Analyze your cluster