Log Starting GCE discovery service – How To Solve Related Issues

Log Starting GCE discovery service – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Starting GCE discovery service” it’s important to understand a few problems related to Elasticsearch concepts cloud-aws, discovery, discovery-gce, instances, plugins. See bellow important tips and explanations on these concepts

Log Context

Log”Starting GCE discovery service” classname is GceInstancesServiceImpl.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        try {
            gceJsonFactory = new JacksonFactory();

            logger.info("starting GCE discovery service");
            // Forcing Google Token API URL as set in GCE SDK to
            //      http://metadata/computeMetadata/v1/instance/service-accounts/default/token
            // See https://developers.google.com/compute/docs/metadata#metadataserver
            String tokenServerEncodedUrl = GceMetadataService.GCE_HOST.get(settings) +

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 Es 5 5 0 Will Not Start Up With Gce  

Es6 4 Will Not Start Up With Gce Di  


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now