Failed to send ping to – How to solve related issues

Failed to send ping to – How to solve related issues

Opster Team

Dec-19, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to send ping to ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: discovery-azure-classic and ping.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

                 if (exp instanceof ConnectTransportException || exp.getCause() instanceof ConnectTransportException ||
                    exp.getCause() instanceof AlreadyClosedException) {
                    // ok; not connected...
                    logger.trace(() -> new ParameterizedMessage("failed to connect to {}"; node); exp);
                } else if (closed == false) {
                    logger.warn(() -> new ParameterizedMessage("failed to send ping to [{}]"; node); exp);
                }
            }
        };
    }


 

Run the Check-Up to get a customized report like this:

Analyze your cluster