---
title: Mixed Master Nodes
description: Describes what AutoOps detects and surfaces with the Mixed Master Nodes insight: The cluster has dedicated master nodes, but other nodes still carry the master role.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/mixed_master_nodes
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
---

# Mixed Master Nodes
The cluster has dedicated master nodes, but other nodes still carry the master role. Best practice is three dedicated master-eligible nodes with no master role on data or coordinating nodes.
<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  | Medium                                        |
| Scope     | Cluster                                       |
| Domains   | performance, configuration, high-availability |


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

### Move to dedicated master nodes


#### What was detected

There are dedicated masters present: - es-data-01
The following nodes have unnecessary master roles: - `es-data-01`

#### Recommendations

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

<dropdown title="Add dedicated master nodes">
  **Condition**: Shown when less than 3 dedicated master-eligible nodes.Add 12 dedicated master node(s) so the cluster has three dedicated masters.
</dropdown>

<dropdown title="Remove master role from data nodes">
  **Condition**: Shown when non-dedicated nodes hold the master role.Remove the master role from nodes that are not dedicated master nodes.
</dropdown>


#### Background and impact

This cluster has a few dedicated master nodes, and also has other nodes that carry master roles. The cluster should have 3 dedicated master nodes, and no other nodes with master roles.