Elasticsearch Disk Watermark: Index Read-Only (FORBIDDEN/12)
Workaround available Self-hosted, Elastic Cloud Updated November 15, 2026Based on 2 user reportsHow we research
Quick answer
At the 95% flood-stage watermark Elasticsearch sets indices read-only-allow-delete and writes fail. The block clears automatically once disk usage falls below the high watermark (90%), or you can remove it manually.
Most likely fix: Free disk first
How to fix it
Try these in order — the most common fix is first.
1. Free disk first
- Delete indices you no longer need, or delete and restore later from a snapshot
- Check usage with GET _cat/allocation
Did this fix it?2. Temporarily raise the watermarks
- PUT _cluster/settings with higher persistent values (Elastic's example: low 90%, high 95%, flood_stage 97%)
- This is a stopgap; reset by setting the same keys to null
Did this fix it?3. Remove the read-only block
- PUT <index>/_settings with index.blocks.read_only_allow_delete set to null
- Needed only if the block did not clear by itself
Did this fix it?4. Fix the root cause
- Add data nodes or disk, keep hardware matched within a tier
- Set ILM retention so old indices are deleted
Did this fix it?
Symptoms
Indexing fails with 'index read-only / allow delete (api)' (FORBIDDEN/12); logs mention flood stage disk watermark exceeded; shards stop allocating at 85%.
Why it happens
- Data node disk above 95% used (defaults: low 85%, high 90%, flood stage 95%)
- Not enough nodes or disk for the data volume
- Old indices never deleted (no ILM retention)
This guide also covers
- elasticsearch index read only allow delete
- elasticsearch disk watermark exceeded
- elasticsearch flood stage disk watermark
Still not working?
If Elasticsearch keeps failing, you're not alone. See every Elasticsearch problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other Elasticsearch errors
- Elasticsearch Cluster Health Yellow: Causes and Fixes
- Elasticsearch Cluster Health Red: How to Fix It
- Elasticsearch Unassigned Shards: Why and How to Fix
- Elasticsearch circuit_breaking_exception: Data Too Large
- Elasticsearch High JVM Memory Pressure and Out of Memory
- Elasticsearch Limit of Total Fields [1000] Exceeded
- Why Is Elasticsearch So Slow? Fixing Slow Searches
- Elasticsearch Cannot Change Field Mapping: Reindex Guide