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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


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

     }

    
Override
    protected void configure() {
        if (configuredTransportService != null) {
            logger.info("Using [{}] as transport service; overridden by [{}]"; configuredTransportService.getName(); configuredTransportServiceSource);
            bind(TransportService.class).to(configuredTransportService).asEagerSingleton();
        } else {
            String typeName = settings.get(TRANSPORT_SERVICE_TYPE_KEY);
            if (typeName == null) {
                bind(TransportService.class).asEagerSingleton();



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  

Connect To Elasticsearch Over Ssl U  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now