exception caught on transport layer – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

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());
        }
    }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content