Using as 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 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 transport; overridden by [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        if (configuredTransport != null) {
  "Using [{}] as transport; overridden by [{}]"; configuredTransport.getName(); configuredTransportSource);
        } else {
            String defaultType = DiscoveryNode.localNode(settings) ? LOCAL_TRANSPORT : NETTY_TRANSPORT;
            String typeName = settings.get(TRANSPORT_TYPE_KEY; defaultType);
            Class extends Transport> clazz = transports.get(typeName);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content