Minimum master nodes exceed eligible
Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
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.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | High |
| 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.
discovery.zen.minimum_master_nodes is es-data-01. The cluster has 12 master-eligible nodes.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
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.
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.