Master failure notification was rejected; its highly likely the node is shutting down – How to solve related issues

Average Read Time

2 Mins

Master failure notification was rejected; its highly likely the node is shutting down – 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 ” Master failure notification was rejected; its highly likely the node is shutting down ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, fault and master.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Master failure notification was rejected; it’s highly likely the node is shutting down” classname is MasterFaultDetection.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     for (Listener listener : listeners) {
                        listener.onMasterFailure(masterNode; cause; reason);
                    }
                });
            } catch (EsRejectedExecutionException e) {
                logger.error("master failure notification was rejected; it's highly likely the node is shutting down"; e);
            }
            stop("master failure; " + reason);
        }
    }





 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content