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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Using as transport; overridden by” it’s important to understand a few problems related to Elasticsearch concepts transport. See bellow important tips and explanations on these concepts

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




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Shield Does Not Work No Credentials  

Shield On Containerized Elasticsear  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now