Cluster read-only allow delete block

A cluster-wide read-only-allow-delete block is enabled. Indexing is blocked, but delete operations can still run so you can free disk space.

Note

For a complete list of insights, refer to AutoOps insights.

Field Value
Component Elasticsearch
Severity High
Scope Cluster
Domains cluster-health

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.

cluster.blocks.read_only_allow_delete is true. Indexing is blocked, but delete operations are still allowed.

Note

AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.

When cluster.blocks.read_only_allow_delete is true, Elasticsearch rejects indexing and updates but still allows deletes. That lets you reclaim disk by deleting indices or documents while writes stay blocked.

Elasticsearch can apply this block automatically when disk usage reaches a critical level (for example flood-stage watermarks). An operator can also set it manually during emergency cleanup.

Until the block is cleared and disk pressure is resolved, applications cannot index new data. Free space first if disk triggered the block, then clear the setting when it is safe to accept writes again.