Low disk usage on data nodes
Data nodes are using only a small share of provisioned disk over time. Ongoing storage charges apply to unused headroom on every affected node.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Node |
| Domains | disk-storage, resource-utilization |
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.
Disk utilization is low on 2 data nodes: es-data-01 and es-data-02.
These nodes are using only 85% of available disk space.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Reduce disk size on data nodes
Condition: Always shown for this insight.
Disk usage on hot nodes is below 48 GB%. Switch to smaller disks to improve utilization while keeping enough headroom for growth.
Reduce data node count
Condition: Always shown for this insight.
Disk usage on hot nodes is below 48 GB%. Scale down the tier if remaining capacity still meets your headroom target.
When provisioned disk stays underused for a sustained period, you pay for storage capacity the cluster is not using.
When data nodes collectively use far less disk than provisioned, storage cost continues for unused headroom. Rightsizing needs a check of retention, replicas, and shard sizing first.
If underutilization continues, storage cost remains higher than the current data footprint requires. Keep enough headroom for expected growth before you rightsize.