Failed to disconnect from possible connection leak – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.2-7.15

Briefly, this error occurs when Elasticsearch is unable to close a connection properly, leading to a potential connection leak. This could be due to a bug in the application or a network issue. To resolve this, you can try the following: 1) Check your application’s code to ensure connections are being closed properly after use. 2) Monitor your network for any irregularities that could be causing connection issues. 3) Update Elasticsearch to the latest version, as this could be a known issue that has been fixed in a newer release.

This guide will help you check for common problems that cause the log ” failed to disconnect from {}; possible connection leak ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “failed to disconnect from {}; possible connection leak” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            public void onFailure(Exception e) {
                assert Thread.holdsLock(mutex) == false : "mutex unexpectedly held";
                // we may not have disconnected; but will not retry; so this connection might have leaked
                logger.warn(new ParameterizedMessage("failed to disconnect from {}; possible connection leak"; discoveryNode); e);
                assert false : "failed to disconnect from " + discoveryNode + "; possible connection leak\n" + e;
                onCompletion(ActivityType.DISCONNECTING; e; connectActivity);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?