---
title: Min Master Node Higher Than Eligible
description: Describes what AutoOps detects and surfaces with the Min Master Node Higher Than Eligible insight: The minimum_master_nodes setting is greater than the number of master-eligible nodes in the cluster.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/min_master_node_higher_than_eligible
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Min Master Node Higher Than Eligible
The minimum_master_nodes setting is greater than the number of master-eligible nodes in the cluster. The cluster might be cannot elect a master and might not start reliably.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value                                       |
|-----------|---------------------------------------------|
| Component | Elasticsearch                               |
| Severity  | High                                        |
| Scope     | Cluster                                     |
| Domains   | configuration, high-availability, stability |


## Example: What you might see in AutoOps

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.

### The value in the minimum_master_nodes setting is greater than the number of eligible master nodes


#### What was detected

Number of nodes with the master role: 12.
Minimum master nodes current settings: es-data-01

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Check minimum master nodes setting">
  **Condition**: Always shown for this insight.Review `discovery.zen.minimum_master_nodes`, or the cluster bootstrapping voting configuration on supported versions, so it matches master-eligible node count and quorum requirements.
</dropdown>

<dropdown title="Check master node is running">
  **Condition**: Always shown for this insight.Confirm master-eligible nodes are running, healthy, and able to participate in master election.
</dropdown>


#### Background and impact

Impact: The cluster will not start.
The value in the setting minimum-master-nodes should be 50% of the number of master eligible nodes in your cluster, rounded up to the nearest integer.