Cluster_shutdown received failed shutdown response master – How to solve related issues

Cluster_shutdown received failed shutdown response master – 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 ” Cluster_shutdown received failed shutdown response master ” 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: admin, cluster, master, node and response.

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 “[cluster_shutdown]: received failed shutdown response master” classname is TransportNodesShutdownAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             logger.trace("[cluster_shutdown]: received shutdown response from master");
                        }

                        
Override
                        public void handleException(TransportException exp) {
                            logger.warn("[cluster_shutdown]: received failed shutdown response master"; exp);
                        }
                    });
                }
            });
            t.start();



 

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

Analyze your cluster