Failed to finalize ping – How to solve related issues

Failed to finalize ping – 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 finalize ping ” 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 and Plugin.

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 finalize ping” classname is MulticastZenPing.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             logger.trace("[{}] sending last pings"; id);
                            sendPingRequest(id);
                            threadPool.schedule(TimeValue.timeValueMillis(timeout.millis() / 4); ThreadPool.Names.GENERIC; new AbstractRunnable() {
                                
Override
                                public void onFailure(Throwable t) {
                                    logger.warn("[{}] failed to finalize ping"; t; id);
                                }

                                
Override
                                protected void doRun() throws Exception {
                                    finalizePingCycle(id; listener);


 

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

Analyze your cluster