---
title: Cluster read-only allow delete block
description: Describes what AutoOps detects and surfaces with the Cluster read-only allow delete block insight: A cluster-wide read-only-allow-delete block is enabled.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/cluster_read_only_allow_delete_block
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# 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](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


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


## Example: What you might see in AutoOps

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.

### The cluster allows only delete operations


#### What was detected

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

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
  ```json

  {
    "transient": {
      "cluster.blocks.read_only": null
    },
    "persistent": {
      "cluster.blocks.read_only": null
    }
  }
  ```

  <note>
    Requires the `manage cluster` privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
  </note>
</dropdown>

<dropdown title="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.
</dropdown>


#### Background and impact

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.