Failed send ping to – How to solve related issues

Failed send ping to – How to solve related issues

Opster Team

Jan-20, 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 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 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 send ping to {}” classname is UnicastZenPing.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 } else if (e instanceof RemoteTransportException) {
                    // something went wrong on the other side
                    logger.debug(() -> new ParameterizedMessage(
                            "[{}] received a remote error as a response to ping {}"; pingingRound.id(); node); e);
                } else {
                    logger.warn(() -> new ParameterizedMessage("[{}] failed send ping to {}"; pingingRound.id(); node); e);
                }
            }

            
Override
            public void onRejection(Exception e) {



 

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

Analyze your cluster