Failed to receive confirmation on sent ping response to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch nodes fail to communicate with each other due to network issues, firewall restrictions, or incorrect configuration. To resolve this, ensure that the network is stable and the nodes are reachable. Check firewall settings to allow communication between nodes. Also, verify the configuration settings in ‘elasticsearch.yml’ file, particularly the ‘discovery.zen.ping.unicast.hosts’ and ‘network.host’, ensuring they are correctly set.

This guide will help you check for common problems that cause the log ” failed to receive confirmation on sent ping response to [{}] ” 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 response.

Log Context

Log “failed to receive confirmation on sent ping response to [{}]” classname is MulticastZenPing.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             } else {
                transportService.sendRequest(requestingNode; ACTION_NAME; multicastPingResponse; new EmptyTransportResponseHandler(ThreadPool.Names.SAME) {
                    
Override
                    public void handleException(TransportException exp) {
                        if (lifecycle.started()) {
                            logger.warn("failed to receive confirmation on sent ping response to [{}]"; exp; requestingNode);
                        }
                    }
                });
            }
        }



 

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?