Master failure notification was rejected it s highly likely the node is shutting down – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when a node in Elasticsearch cluster is shutting down and it rejects the master failure notification. This could be due to network issues, heavy load, or a slow cluster state processing. To resolve this issue, you can try the following: 1) Check the health of your cluster and ensure all nodes are running properly. 2) Monitor the load on your nodes and adjust as necessary. 3) Review your cluster state processing time and optimize if needed. 4) Ensure your network connectivity is stable.

This guide will help you check for common problems that cause the log ” Master failure notification was rejected; it’s 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.

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);
        }
    }





 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?