High CPU on node
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
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.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Node |
| Domains | performance, cpu, stability |
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.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
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.