Failed to send third ping request – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to send a third ping request to another node in the cluster. This could be due to network issues, firewall restrictions, or the target node being unresponsive. To resolve this issue, you can check the network connectivity between the nodes, ensure that the firewall is not blocking the ping requests, and verify that the target node is functioning properly. Additionally, you can also check the Elasticsearch logs for more detailed information about the error.

This guide will help you check for common problems that cause the log ” [{}] failed to send third ping request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, discovery-multicast, ping, Plugin and request.

Log Context

Log “[{}] failed to send third ping request” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void doRun() {
                    threadPool.schedule(TimeValue.timeValueMillis(timeout.millis() / 2); ThreadPool.Names.GENERIC; new AbstractRunnable() {
                        public void onFailure(Throwable t) {
                            logger.warn("[{}] failed to send third ping request"; t; id);
                            finalizePingCycle(id; listener);

                        public void doRun() {


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?