Opster Team
Before you begin reading this guide, we recommend you run 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 ” exception caught on transport layer ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: netty.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.
Log Context
Log “exception caught on transport layer [{}]; closing connection” classname is NettyTransport.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
future.getChannel().close(); } }); } } else { logger.warn("exception caught on transport layer [{}]; closing connection"; e.getCause(); ctx.getChannel()); // close the channel; which will cause a node to be disconnected if relevant ctx.getChannel().close(); disconnectFromNodeChannel(ctx.getChannel(); e.getCause()); } }
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 3 minutes
Billy McCarthy
Senior SysAdmin at Backblaze