Desired nodes not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.1-8.9

Briefly, this error occurs when Elasticsearch is unable to locate the nodes specified in a request. This could be due to incorrect node names, network issues, or the nodes being down. To resolve this, ensure the node names are correct and the nodes are up and running. Check your network connectivity and firewall settings. If the nodes are part of a cluster, ensure the cluster is properly configured and functioning. Also, check the Elasticsearch logs for any additional information about the issue.

This guide will help you check for common problems that cause the log ” Desired nodes not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster.

Log Context

Log “Desired nodes not found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ClusterState state;
 ActionListener listener
 ) throws Exception {
 final DesiredNodes latestDesiredNodes = DesiredNodes.latestFromClusterState(state);
 if (latestDesiredNodes == null) {
 listener.onFailure(new ResourceNotFoundException("Desired nodes not found"));
 } else {
 listener.onResponse(new GetDesiredNodesAction.Response(latestDesiredNodes));


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?