Exception while closing channels – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Exception while closing channels ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: handler.

Log Context

Log “exception while closing channels” classname is AbstractHttpServerTransport.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         synchronized (httpServerChannels) {
            if (httpServerChannels.isEmpty() == false) {
                try {
                    CloseableChannel.closeChannels(new ArrayList(httpServerChannels); true);
                } catch (Exception e) {
                    logger.warn("exception while closing channels"; e);
                } finally {
                    httpServerChannels.clear();
                }
            }
        }




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content