Starting GCE discovery service – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to use Google Compute Engine (GCE) for node discovery but encounters issues. This could be due to incorrect configuration settings or network connectivity problems. To resolve this, ensure that the Elasticsearch cluster is correctly configured to use GCE for discovery. Check the network connectivity between your Elasticsearch nodes and GCE. Also, verify that the necessary permissions and API access are correctly set up in GCE. If the problem persists, consider using a different discovery method.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

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?