Using as http transport; overridden by – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Using as http transport; overridden by ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: transport.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Using [{}] as http transport; overridden by [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    public void setHttpServerTransport(Class extends HttpServerTransport> httpServerTransport; String source) {
        Preconditions.checkNotNull(httpServerTransport; "Configured http server transport may not be null");
        Preconditions.checkNotNull(source; "Plugin; that changes transport may not be null");"Using [{}] as http transport; overridden by [{}]"; httpServerTransportClass.getName(); source);
        this.httpServerTransportClass = httpServerTransport;


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content