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 Elasticsearch is unable to retrieve the list of nodes from Azure. This could be due to network connectivity issues, incorrect configuration settings, or Azure service disruptions. To resolve this issue, you can check your network connection, verify your Azure configuration settings, or check Azure service status. Additionally, ensure that your Elasticsearch cluster has the necessary permissions to access Azure resources.
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 ” can not get list of azure nodes: [{}]. Returning empty list of nodes. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, plugins, discovery-azure-classic, discovery.
Log Context
Log “can not get list of azure nodes: [{}]. Returning empty list of nodes.” classname is AzureSeedHostsProvider.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;
