Failed to get node info for ; disconnecting. – How to solve related issues

Average Read Time

2 Mins

Failed to get node info for ; disconnecting. – 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 ” Failed to get node info for ; disconnecting. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: client and node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Failed to get node info for {}; disconnecting…” classname is TransportClientNodesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     }
                } catch (ConnectTransportException e) {
                    logger.debug(() -> new ParameterizedMessage("failed to connect to node [{}]; ignoring..."; listedNode); e);
                    hostFailureListener.onNodeDisconnected(listedNode; e);
                } catch (Exception e) {
                    logger.info(() -> new ParameterizedMessage("failed to get node info for {}; disconnecting..."; listedNode); e);
                }
            }

            nodes = establishNodeConnections(newNodes);
            filteredNodes = Collections.unmodifiableList(newFilteredNodes);




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content