---
title: Minimum master nodes exceed eligible
description: Describes what AutoOps detects and surfaces with the Minimum master nodes exceed eligible insight: `discovery.zen.minimum_master_nodes` exceeds the number of master-eligible nodes in the cluster.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/minimum_master_nodes_exceed_eligible
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Minimum master nodes exceed eligible
`discovery.zen.minimum_master_nodes` exceeds the number of master-eligible nodes in the cluster. The cluster might fail to elect a master or fail to start because the setting demands more masters than exist.
<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.

### Minimum master nodes setting exceeds eligible master nodes


#### What was detected

`discovery.zen.minimum_master_nodes` is es-data-01. The cluster has 12 master-eligible nodes.

#### 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

`discovery.zen.minimum_master_nodes` is the legacy Zen discovery quorum setting. On older Elasticsearch versions it defined how many master-eligible nodes must agree before a master can be elected. Modern Elasticsearch uses automatic voting configuration, but this setting can remain on legacy or upgraded clusters.
When the value is greater than the number of master-eligible nodes, master election cannot succeed. The cluster might fail to start or stay without an elected master until you add master-eligible nodes or lower the setting to match your topology.

## Guide

[Quorum-based decision making](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-quorums)