Failed to send second ping request – How to solve related issues

Average Read Time

2 Mins

Failed to send second ping request – How to solve related issues

Opster Team

Feb-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 to send second ping request ” 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, discovery-multicast, ping, Plugin and request.

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

{{mpg_logstarted}}

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

             // try and send another ping request halfway through (just in case someone woke up during it...)
            // this can be a good trade-off to nailing the initial lookup or un-delivered messages
            threadPool.schedule(TimeValue.timeValueMillis(timeout.millis() / 2); ThreadPool.Names.GENERIC; new AbstractRunnable() {
                
Override
                public void onFailure(Throwable t) {
                    logger.warn("[{}] failed to send second ping request"; t; id);
                    finalizePingCycle(id; listener);
                }

                
Override
                public void doRun() {


 

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

Analyze your cluster