Log Using as http transport; overridden by – How To Solve Related Issues


Log 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 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 ” Using as http transport; overridden by ” 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: transport.

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 “Using [{}] as http transport; overridden by [{}]” classname is HttpServerModule.java
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");
        logger.info("Using [{}] as http transport; overridden by [{}]"; httpServerTransportClass.getName(); source);
        this.httpServerTransportClass = httpServerTransport;
    }
}






 





Optimize Elasticsearch Performance

Try The Tool