# FORBIDDEN/12/index read-only / allow delete (api)

**URL:** <https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/126067>\
**Category:** Elasticsearch\
**Created:** [March 29, 2018, 9:58am UTC](https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/126067 "2018-03-29T09:58:37Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\
**Post date:** [March 30, 2018, 5:48pm UTC](https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/126067/12 "2018-03-30T17:48:16Z")

</div>

Once you hit the floodstage watermark (95% by default), you must manually release the index lock — see [https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html). The following will do the trick, which you need to run for every affected index:

```
PUT /your-index/_settings
{
  "index.blocks.read_only_allow_delete": null
}

```

PS: Please properly format your code; it's pretty hard to read otherwise.

---

_[View the full topic](https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/126067)._