Many deleted docs
Some indices retain a large share of documents marked deleted but not yet merged away. Those tombstones still use disk and add work during searches.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Index |
| Domains | disk-storage, index-management |
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.
There are many deleted documents that are still taking up disk space in some indices. For example, the index with highest deleted docs ratio is: | Index name | Index size | Total docs | Deleted docs |
| ---------------------------- | ---------- | --------- | -------------------- |
| logs-prod-000045 | 500 GB | 42,000,000 | 85% |
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Force merge deleted documents
Condition: Always shown for this insight.
Run a force merge with only_expunge_deletes=true on logs-prod-000045, logs-prod-000046 to reclaim disk used by deleted documents. Use the action below.
POST logs-archive-000001/_forcemerge?only_expunge_deletes=true
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
Reindex indices
Condition: Always shown for this insight.
Reindex indices with many deleted documents into new indices. After reindex completes, delete the old indices to reclaim disk space.
Removing deleted documents from an index is good practice because it saves storage space, improves search performance, maintains data accuracy, and simplifies index management.