---
title: Loaded Master Nodes
description: Describes what AutoOps detects and surfaces with the Loaded Master Nodes insight: Master-eligible nodes show uneven CPU or load, which might or might not be expected.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/loaded_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
---

# Loaded Master Nodes
Master-eligible nodes show uneven CPU or load, which might or might not be expected. Only one node acts as elected master at a time, so higher use on that node can be normal.
<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     | Node                                              |
| Domains   | performance, cluster-health, resource-utilization |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                                 | Type    | Default |
|-----------------------------------------|---------|---------|
| Loaded node load percent above baseline | Integer | 180     |
| Successive samplings to trigger         | Integer | 3       |
| The minimum value to consider as high   | Integer | 1       |


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

### Some master-eligible nodes are more loaded than others: `es-data-01`


#### What was detected

The affected node/s are: `es-data-01` and `es-data-02` High search activity indices:`logs-prod-000045` High indexing activity indices:`logs-prod-000045`

#### Recommendations

No recommendations are linked to this insight.

#### Background and impact

Impact: This might cause a bottleneck to form and reduce administrative task performance.
The master node load is unbalanced. The CPU and load on some master nodes is higher than on others.
This is normal if the loaded master node is the elected master, as only one master node is active at any one time. If the CPU or load is very high on one or more master-eligible nodes, performance could begin to be impacted as the cluster becomes unstable.