Node-left with reason – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.7-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a node in the Elasticsearch cluster becomes unavailable or leaves the cluster. 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 logs for any errors, ensure the node is running and reachable, check the network connectivity, and verify the hardware is functioning properly. If the node was intentionally shut down, you may need to reconfigure your cluster to handle the loss of the node.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

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

                logger.debug("node [{}] does not exist in cluster state; ignoring"; task);
                reason = null;
            taskContext.success(() -> {
                if (reason != null) {
          "node-left: [{}] with reason [{}]"; task.node().descriptionWithoutAttributes(); reason);


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?