---
title: Master-eligible node added
description: Describes what AutoOps detects and surfaces with the Master-eligible node added insight: A master-eligible node joined the cluster topology.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/master_eligible_node_added
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
---

# Master-eligible node added
A master-eligible node joined the cluster topology. Adding masters changes voting membership and can shift election behavior during cluster-state updates.
<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  | Low                                                       |
| Scope     | Cluster                                                   |
| Domains   | performance, high-availability, node-lifecycle, 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.

### Master-eligible node was added to cluster


#### What was detected

A master-eligible node joined the cluster: es-data-01.

#### Recommendations

No recommendations are linked to this insight.

#### Background and impact

Master-eligible nodes participate in cluster coordination and master elections. Adding a master-eligible node changes voting membership and can shift election behavior.
An odd number of master-eligible nodes is recommended so the cluster can maintain quorum during failures. After a topology change, brief cluster-state activity is normal while the cluster adjusts.

## Guide

[Bootstrapping a cluster](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-bootstrap-cluster)