Log Unable to resolve default zone from metadata server for GCE discovery service – How To Solve Related Issues



Log 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 read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

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. 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: 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

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 {






Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 On Parse Error Can Not Construct In

2 About The Elasticsearch Category






Optimize Elasticsearch Performance

Try The Tool