Cluster read-only allow delete block
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
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.
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.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Clear cluster read-only block
Condition: Shown when enough disk space.
Clear the cluster read-only block so indexing can resume. Use the action below, or set cluster.blocks.read_only to null in cluster settings.
PUT _cluster/settings{ "transient": { "cluster.blocks.read_only": null }, "persistent": { "cluster.blocks.read_only": null } }
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
Free disk before clearing read-only block
Condition: Shown when not enough disk space.
Disk space is critically low. Increase disk space or delete old indices before you clear the read-only block. Deleting indices is permanent; confirm backups first.
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.