Using as transport overridden by – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when the transport method specified in the Elasticsearch configuration is overridden by another setting. This could be due to a conflict in the configuration files or an incorrect setting. To resolve this issue, you can check the Elasticsearch configuration files for any conflicting settings and correct them. Alternatively, you can specify the correct transport method in the Elasticsearch settings. If the error persists, consider resetting the configuration to its default settings and reconfiguring it.

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.

Log Context

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

             }
        }

        bind(NamedWriteableRegistry.class).toInstance(namedWriteableRegistry);
        if (configuredTransport != null) {
            logger.info("Using [{}] as transport; overridden by [{}]"; configuredTransport.getName(); configuredTransportSource);
            bind(Transport.class).to(configuredTransport).asEagerSingleton();
        } 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);




 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?