# Remove index.blocks.read\_only\_allow\_delete blocks when nodes recover from high disk utilization

**URL:** <https://discuss.elastic.co/t/remove-index-blocks-read-only-allow-delete-blocks-when-nodes-recover-from-high-disk-utilization/169270>\
**Category:** Elasticsearch\
**Created:** [February 20, 2019, 5:38pm UTC](https://discuss.elastic.co/t/remove-index-blocks-read-only-allow-delete-blocks-when-nodes-recover-from-high-disk-utilization/169270 "2019-02-20T17:38:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bukhtawar\_Khan](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@Bukhtawar\_Khan](https://discuss.elastic.co/u/Bukhtawar_Khan)\
**Post date:** [February 20, 2019, 5:38pm UTC](https://discuss.elastic.co/t/remove-index-blocks-read-only-allow-delete-blocks-when-nodes-recover-from-high-disk-utilization/169270/1 "2019-02-20T17:38:36Z")

</div>

As a part of applying flood stage watermark we apply a block `index.blocks.read_only_allow_delete blocks` which is expected to be removed manually. Can't this be automated to unblock all indices and re-evaluate the block logic.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 20, 2019, 5:38pm UTC](https://discuss.elastic.co/t/remove-index-blocks-read-only-allow-delete-blocks-when-nodes-recover-from-high-disk-utilization/169270/2 "2019-03-20T17:38:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.