How To Solve Issues Related to Log – Caught exception while handling client http traffic; closing connection

How To Solve Issues Related to Log – Caught exception while handling client http traffic; closing connection

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Caught exception while handling client http traffic; closing connection” it’s important to understand a few problems related to Elasticsearch concepts client, netty. See bellow important tips and explanations on these concepts

Log Context

Log”Caught exception while handling client http traffic; closing connection {}” classname is NettyHttpServerTransport.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (!lifecycle.started()) {
                // ignore
                return;
            }
            if (!NetworkExceptionHelper.isCloseConnectionException(e.getCause())) {
                logger.warn("Caught exception while handling client http traffic; closing connection {}"; e.getCause(); ctx.getChannel());
                ctx.getChannel().close();
            } else {
                logger.debug("Caught exception while handling client http traffic; closing connection {}"; e.getCause(); ctx.getChannel());
                ctx.getChannel().close();
            }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

 

Caught Exception While Handling Cli  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now