Log Unable to shutdown GCE Http Transport – How To Solve Related Issues


Log Unable to shutdown GCE Http Transport – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Unable to shutdown GCE Http Transport ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cloud-aws, discovery-gce, metadata and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 {
                gceHttpTransport.shutdown();
            } catch (IOException e) {
                logger.warn("unable to shutdown GCE Http Transport"; e);
            }
            gceHttpTransport = null;
        }
    }





 

Optimize Elasticsearch Performance

Try The Tool