Failed to send ping transport message – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch nodes fail to communicate with each other due to network issues, firewall restrictions, or incorrect configuration settings. To resolve this, ensure that the network connection between nodes is stable and reliable. Check firewall settings to allow inter-node communication. Verify the configuration settings, particularly the ‘transport.ping_schedule’ and ‘transport.tcp.connect_timeout’ parameters. Also, ensure that the nodes are running compatible Elasticsearch versions.

This guide will help you check for common problems that cause the log ” failed to send ping transport message ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: ping.

Log Context

Log “failed to send ping transport message” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            threadPool.scheduleUnlessShuttingDown(pingInterval; ThreadPool.Names.GENERIC; this);

        public void onFailure(Exception e) {
            logger.warn("failed to send ping transport message"; e);

        private boolean needsKeepAlivePing(TcpChannel channel) {
            TcpChannel.ChannelStats stats = channel.getChannelStats();
            long accessedDelta = stats.lastAccessedTime() - lastPingRelativeMillis;


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?