Briefly, this error occurs when the default transport service of Elasticsearch is overridden by a custom transport service. This could be due to a configuration error or a plugin that modifies the transport service. To resolve this issue, you can check your Elasticsearch configuration for any settings that might be overriding the default transport service. If a plugin is causing the issue, you may need to disable or reconfigure it. Alternatively, you can revert to the default transport service if the custom one is not necessary.
This guide will help you check for common problems that cause the log ” Using [{}] as transport service; 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 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();
[ratemypost]
