Unable to shutdown GCE Http Transport – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch fails to close the Google Cloud Engine (GCE) HTTP transport connection during the shutdown process. This could be due to network issues, incorrect configuration, or a bug in the Elasticsearch GCE plugin. To resolve this issue, you can try to: 1) Check and correct the GCE configuration settings in Elasticsearch, 2) Update the Elasticsearch GCE plugin to the latest version, 3) Investigate network issues that might be preventing the shutdown, or 4) Restart the Elasticsearch service.

This guide will help you check for common problems that cause the log ” unable to shutdown GCE Http Transport ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins, discovery-gce.

Log Context

Log “unable to shutdown GCE Http Transport” classname is GceMetadataService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    protected void doStop() {
        if (gceHttpTransport != null) {
            try {
            } catch (IOException e) {
                logger.warn("unable to shutdown GCE Http Transport"; e);
            gceHttpTransport = null;


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?