Starting 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Starting 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 plugins.

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) +
                "/computeMetadata/v1/instance/service-accounts/default/token";




 

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?

Analyze your cluster & get personalized recommendations

Skip to content