How To Solve Issues Related to Log – Master failure notification was rejected; its highly likely the node is shutting down

How To Solve Issues Related to Log – Master failure notification was rejected; its highly likely the node is shutting down

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Master failure notification was rejected; its highly likely the node is shutting down” it’s important to understand a few problems related to Elasticsearch concepts discovery, fault, master. See bellow important tips and explanations on these concepts

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





Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 19842  

Cluster Instability If Master Leade  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now