---
title: High CPU On Node
description: Describes what AutoOps detects and surfaces with the High CPU On Node insight: CPU utilization on a node has stayed high for a sustained period.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/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 has stayed high for a sustained period. 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://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/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.

### The CPU utilization is high on node: `es-data-01`


#### What was detected

_No description available._

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

Impact: High CPU utilization on nodes will cause high search and indexing latencies, rejected requests and possible time-outs.
There can be a number of causes for high CPU. It is usually a symptom of other underlying issues, such as configuration or suboptimal queries.
These causes should be investigated and fixed, because a distressed node can slow down query responses and even cause the node to disconnect from the cluster.