Min Master Node Higher Than Quorum
The minimum_master_nodes setting is higher than the quorum needed for a majority of master-eligible nodes. If one or more master nodes are lost, the cluster might refuse to elect a new master even when enough nodes remain.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Cluster |
| Domains | configuration, high-availability, stability |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
Number of nodes with the master role: 12. Minimum master nodes current settings: es-data-01
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Set minimum master nodes quorum
Condition: Always shown for this insight.
Set discovery.zen.minimum_master_nodes to 2 in each node's config, then rolling-restart master-eligible nodes so the quorum takes effect.
Impact: If one or more master nodes are lost, this setting would cause the cluster not to start. The value in this setting should be 50% of the number of master eligible nodes rounded up to the nearest integer. If the value set in the minimum_master_nodes setting is higher than this, it’s possible that in the event of one or more master nodes being lost this setting will prevent the cluster from starting, despite it actually having sufficient quorum of master eligible nodes do so.