Loaded master-eligible nodes
Some master-eligible nodes show materially higher CPU utilization than their peers. Higher use on the elected master can be normal; sustained high load on other master-eligible nodes can delay cluster-state updates.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, cluster-health, resource-utilization |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| CPU percent above peer baseline | Integer | 180 |
| Consecutive samples meeting the imbalance conditions | Integer | 3 |
| Minimum CPU utilization to consider a node loaded | Integer | 1 |
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.
CPU utilization on es-data-01 and es-data-02 is sustained above the peer baseline for master-eligible nodes.
Indices with high search activity:
logs-prod-000045Indices with high indexing activity:
logs-prod-000045
No recommendations are linked to this insight.
Only one master-eligible node is elected master at a time, so higher CPU on that node can be expected. When other master-eligible nodes stay much busier than their peers, cluster-state updates and administrative tasks can slow down and the cluster can become less stable.
Confirm which node is elected master before treating every imbalance as a problem.