Briefly, this error occurs when the default HTTP transport protocol in Elasticsearch is overridden by another setting in the configuration file. This could be due to a misconfiguration or an intentional change. To resolve this issue, you can either revert to the default setting by removing the overriding configuration or ensure that the overriding configuration is correctly set up. If the error persists, you may need to check for compatibility issues between the HTTP transport protocol and the version of Elasticsearch you are using.
This guide will help you check for common problems that cause the log ” Using [{}] as http 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 http transport; overridden by [{}]” classname is HttpServerModule.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
public void setHttpServerTransport(Class extends HttpServerTransport> httpServerTransport; String source) {
Preconditions.checkNotNull(httpServerTransport; "Configured http server transport may not be null");
Preconditions.checkNotNull(source; "Plugin; that changes transport may not be null");
logger.info("Using [{}] as http transport; overridden by [{}]"; httpServerTransportClass.getName(); source);
this.httpServerTransportClass = httpServerTransport;
}
}
[ratemypost]