Unable to resolve default zone from metadata server for GCE discovery service – Elasticsearch Log Diagnostic

Remediate Elasticsearch Issues

Opster detects and predicts root causes of Elasticsearch problems

Learn More

Opster has analyzed this log so you don’t have to
Navigate directly to one of the sections in this page :

Troubleshooting Background – start here to get the full picture       
Log Context – usefull for experts
Related Issues – selected resources from the community  
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check My Elasticsearch 

Troubleshooting background

To troubleshoot Elasticsearch log “Unable to resolve default zone from metadata server for GCE discovery service” it’s important to know common problems related to Elasticsearch concepts: cloud-aws, discovery, discovery-gce, instances, metadata, plugins. See below-detailed explanations complete with common problems, examples and useful tips.

Log Context

Log ”Unable to resolve default zone from metadata server for GCE discovery service” classname is GceInstancesServiceImpl.java
To help get the right context about this log, we have extracted the following from Elasticsearch source code

         try {
            final String defaultZone =
            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 {

To help troubleshoot related issues we have gathered selected answers from STOF & Discuss and issues from Github, please review the following for further information :

On Parse Error Can Not Construct In


About The Elasticsearch Category


About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)