Can not get list of azure nodes: . Returning empty list of nodes. – How to solve related issues

Average Read Time

2 Mins

Can not get list of azure nodes: . Returning empty list of nodes. – 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 ” 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: discovery, discovery-azure-classic, hosts, plugins and repository-azure.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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;




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content