Fetching nodes from external cluster failed version 6.8 – How to solve related issues

Average Read Time

2 Mins

Fetching nodes from external cluster failed version 6.8 – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Fetching nodes from external cluster failed version 6.8 ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster and node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

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 :

                     }
                    listener.onResponse(null);
                } catch (CancellableThreads.ExecutionCancelledException ex) {
                    listener.onFailure(ex); // we got canceled - fail the listener and step out
                } catch (Exception ex) {
                    logger.warn(() -> new ParameterizedMessage("fetching nodes from external cluster {} failed"; clusterAlias); ex);
                    collectRemoteNodes(seedNodes; transportService; connectionManager; listener);
                }
            }

            
Override



 

Run the Check-Up to get a customized report like this:

Analyze your cluster