---
title: High CPU on node
description: Describes what AutoOps detects and surfaces with the High CPU on node insight: CPU utilization on a node is above 80% in the latest checkup snapshot.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/high_cpu_on_node
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
---

# High CPU on node
CPU utilization on a node is above 80% in the latest checkup snapshot. Search and indexing latencies tend to rise, and the node might reject work or time out requests.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://www.elastic.co/docs/reference/autoops-insights/elasticsearch).
</note>


## Insight details


| Field     | Value                       |
|-----------|-----------------------------|
| Component | Elasticsearch               |
| Severity  | Medium                      |
| Scope     | Node                        |
| Domains   | performance, cpu, 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.

### CPU utilization is high on es-data-01


#### What was detected

CPU utilization is high on es-data-01.

#### Recommendations

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

<dropdown title="Add cluster capacity for high CPU">
  **Condition**: Always shown for this insight.CPU utilization is high on https://localhost:9200. Add cores or data nodes, or find and fix the workload causing sustained high CPU.
</dropdown>


#### Background and impact

High CPU on a node increases search and indexing latency and can lead to rejected requests or timeouts. It is usually a symptom of underlying pressure such as expensive queries, heavy ingest, or configuration that keeps the node saturated.
If the node stays distressed, query responses slow further and the node can disconnect from the cluster.