Failed to disconnect to node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch encounters issues while trying to disconnect from a node. This could be due to network problems, node unresponsiveness, or abrupt termination of a node. To resolve this, you can check the network connectivity and ensure it’s stable. If the node is unresponsive, try restarting it. If the issue persists, check the cluster health and node logs for any anomalies. Also, ensure that the Elasticsearch version is up-to-date and compatible across all nodes.

This guide will help you check for common problems that cause the log ” failed to disconnect to node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, node.

Log Context

Log “failed to disconnect to node [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                Integer current = nodes.remove(node);
                assert current != null : "node " + node + " was removed in event but not in internal nodes";
                try {
                } catch (Exception e) {
                    logger.warn(() -> new ParameterizedMessage("failed to disconnect to node [{}]"; node); 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?