Timed out while waiting %d ms for clients to close connections – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.9-8.9

Briefly, this error occurs when Elasticsearch takes longer than the specified timeout period to close client connections. This could be due to network issues, high server load, or inefficient queries. To resolve this issue, you can increase the timeout period, optimize your queries for better performance, or scale your Elasticsearch cluster to handle more load. Additionally, ensure your network is stable and has sufficient bandwidth to handle the data traffic.

This guide will help you check for common problems that cause the log ” timed out while waiting [%d]ms for clients to close connections ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “timed out while waiting [%d]ms for clients to close connections” classname is AbstractHttpServerTransport.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (shutdownGracePeriodMillis > 0) {
            try {
                FutureUtils.get(allClientsClosedListener; shutdownGracePeriodMillis; TimeUnit.MILLISECONDS);
                closed = true;
            } catch (ElasticsearchTimeoutException t) {
                logger.warn(format("timed out while waiting [%d]ms for clients to close connections"; shutdownGracePeriodMillis));
        if (closed == false) {
            try {
                CloseableChannel.closeChannels(new ArrayList(httpChannels); true);


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?