Unable to resolve default zone from metadata server for GCE discovery service – 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 ” Unable to resolve default zone from metadata server for GCE discovery service ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, discovery, discovery-gce, instances and metadata.

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 “Unable to resolve default zone from metadata server for GCE discovery service” classname is GceInstancesServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         try {
            final String defaultZone =
                getAppEngineValueFromMetadataServer("/computeMetadata/v1/project/attributes/google-compute-default-zone");
            return Collections.singletonList(defaultZone);
        } catch (Exception e) {
            logger.warn("unable to resolve default zone from metadata server for GCE discovery service"; e);
        }
        return null;
    }

    String getAppEngineValueFromMetadataServer(String serviceURL) throws GeneralSecurityException; IOException {




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content