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

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Prevent Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Using as transport; overridden by” it’s important to understand common problems related to Elasticsearch concepts: transport. See detailed explanations below complete with common problems, examples and useful tips.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Shield Does Not Work No Credentials  

2Shield On Containerized Elasticsear  

Log Context

Log ”Using [{}] as transport; overridden by [{}]” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :

<pre class="wp-block-syntaxhighlighter-code">             }

        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);


About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster