# Blocks.write = true, won't work

**URL:** <https://discuss.elastic.co/t/blocks-write-true-wont-work/222464>\
**Category:** Elasticsearch\
**Created:** [March 6, 2020, 1:30pm UTC](https://discuss.elastic.co/t/blocks-write-true-wont-work/222464 "2020-03-06T13:30:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aliservetdonmez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aliservetdonmez/32/41762_2.png) [@aliservetdonmez](https://discuss.elastic.co/u/aliservetdonmez)\
**Post date:** [March 6, 2020, 1:30pm UTC](https://discuss.elastic.co/t/blocks-write-true-wont-work/222464/1 "2020-03-06T13:30:18Z")

</div>

Hi,

I am running an ES (version 6.3.1) cluster on AWS's managed-ES service, and have a script (written in Python) that is running every so often to check for index sizes, and if any index exceeds a given threshold, I will set that index's `index.blocks.write` setting to `true` via `'curl --fail --request PUT "%(_host)s/%(index)s/_settings" -H \'Content-Type: application/json\' -d "{ \\"index\\": { \\"blocks.write\\": true } }"'`.

Given every time I make the `curl` request above, the answer is always `{"acknowledged":true}`, I am having hard time understanding, and troubleshooting, why clients are still able to write to now, in theory, write-blocked indices via the `_bulk` endpoint anyway.

Is there any setting that allows clients to set back indices to write-allowed mode automagically? Is there anyway I can see what and reason an index goes back to `blocks.write: false` "by itself"?

Thank you.

---

<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:** [April 3, 2020, 1:30pm UTC](https://discuss.elastic.co/t/blocks-write-true-wont-work/222464/2 "2020-04-03T13:30:19Z")

</div>

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