Removing node from cluster info – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.11

Briefly, this error occurs when a node in the Elasticsearch cluster is not responding or is disconnected. This could be due to network issues, hardware failure, or the node being shut down. To resolve this issue, you can check the node’s network connectivity, ensure the hardware is functioning properly, or restart the node if it was shut down. If the node is consistently problematic, consider removing it permanently and replacing it with a new one.

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

Log Context

Log “Removing node from cluster info: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        // Clean up info for any removed nodes
        for (DiscoveryNode removedNode : event.nodesDelta().removedNodes()) {
            if (removedNode.isDataNode()) {
                logger.trace("Removing node from cluster info: {}"; removedNode.getId());
                if (leastAvailableSpaceUsages.containsKey(removedNode.getId())) {
                    ImmutableOpenMap.Builder newMaxUsages = ImmutableOpenMap.builder(leastAvailableSpaceUsages);
                    leastAvailableSpaceUsages =;


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?