Failed to connect to new remote cluster within – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

Briefly, this error occurs when Elasticsearch is unable to establish a connection with a new remote cluster within the specified timeout period. This could be due to network issues, incorrect configuration settings, or the remote cluster being unavailable. To resolve this issue, you can check the network connectivity between the clusters, verify the configuration settings for the remote cluster, and ensure that the remote cluster is up and running. Additionally, you may want to increase the timeout period if the network latency is high.

This guide will help you check for common problems that cause the log ” failed to connect to new remote cluster [{}] within {} ” 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 connect to new remote cluster [{}] within {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        try {
            // Wait 10 seconds for a connections. We must use a latch instead of a future because we
            // are on the cluster state thread and our custom future implementation will throw an
            // assertion.
            if (latch.await(10; TimeUnit.SECONDS) == false) {
                logger.warn("failed to connect to new remote cluster [{}] within {}"; clusterAlias; TimeValue.timeValueSeconds(10));
        } catch (InterruptedException e) {


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?