Fetching nodes from external cluster failed – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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

Log Context

Log “Fetching nodes from external cluster [{}] failed” classname is RemoteClusterConnection.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else {
                    listener.onFailure(new IllegalStateException("no seed node left"));
            } catch (CancellableThreads.ExecutionCancelledException ex) {
                logger.warn(() -> new ParameterizedMessage("fetching nodes from external cluster [{}] failed"; clusterAlias); ex);
                listener.onFailure(ex); // we got canceled - fail the listener and step out
            } catch (ConnectTransportException | IOException | IllegalStateException ex) {
                // ISE if we fail the handshake with an version incompatible node
                if (seedNodes.hasNext()) {
                    logger.debug(() -> new ParameterizedMessage("fetching nodes from external cluster [{}] failed moving to next node";


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?

Analyze your cluster & get personalized recommendations

Skip to content