This is not an HTTP port – Elasticsearch Error How To Solve Related Issues


This is not an HTTP port – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” This is not an HTTP port ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”This is not an HTTP port”classname  is TcpTransport.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 
  private static int readHeaderBuffer(BytesReference headerBuffer) throws IOException {
  if (headerBuffer.get(0) != 'E' || headerBuffer.get(1) != 'S') {
  if (appearsToBeHTTPRequest(headerBuffer)) {
  throw new HttpRequestOnTransportException("This is not an HTTP port");
  }
 
  if (appearsToBeHTTPResponse(headerBuffer)) {
  throw new StreamCorruptedException("received HTTP response on transport port; ensure that transport port (not " +
  "HTTP port) of a remote node is specified in the configuration");

 

Optimize Elasticsearch Performance

Try The Tool