Unable to resolve default zone from metadata server for GCE discovery service – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot retrieve the default zone information from the metadata server for Google Compute Engine (GCE) discovery service. This could be due to network issues, incorrect configuration, or lack of necessary permissions. To resolve this, ensure that your Elasticsearch instance has the correct permissions to access the metadata server. Also, verify your GCE discovery service configuration in Elasticsearch, making sure it’s correctly set up. Lastly, check your network connectivity to ensure the metadata server is reachable.

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: metadata, plugins, discovery-gce, discovery.

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 :

            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 {

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?