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. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Can not get list of azure nodes: . Returning empty list of nodes. (version 6.8) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-azure-classic, hosts and repository-azure.
Log Context
Log “Can not get list of azure nodes: [{}]. Returning empty list of nodes.” classname is AzureUnicastHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} catch (AzureServiceDisableException e) {
logger.debug("Azure discovery service has been disabled. Returning empty list of nodes.");
return dynamicHosts;
} catch (AzureServiceRemoteException e) {
// We got a remote exception
logger.warn("can not get list of azure nodes: [{}]. Returning empty list of nodes."; e.getMessage());
logger.trace("AzureServiceRemoteException caught"; e);
return dynamicHosts;
}
InetAddress ipAddress = null;
Find & fix Elasticsearch problems
