# Error FORBIDDEN/8/index write (api)\] and Elasticsearch stop to receiving logstash bulk requests

**URL:** https://discuss.elastic.co/t/error-forbidden-8-index-write-api-and-elasticsearch-stop-to-receiving-logstash-bulk-requests/215028
**Category:** Logstash
**Created:** [January 14, 2020, 6:05pm UTC](https://discuss.elastic.co/t/error-forbidden-8-index-write-api-and-elasticsearch-stop-to-receiving-logstash-bulk-requests/215028 "2020-01-14T18:05:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ALEXANDRE\_BUNN1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexandre_bunn1/32/60793_2.png) [@ALEXANDRE\_BUNN1](https://discuss.elastic.co/u/ALEXANDRE_BUNN1)
#### Post date: [January 15, 2020, 4:55pm UTC](https://discuss.elastic.co/t/error-forbidden-8-index-write-api-and-elasticsearch-stop-to-receiving-logstash-bulk-requests/215028/2 "2020-01-15T16:55:46Z")

</div>

As a workaroud I've executed the command below.

curl -X PUT -H "Content-Type: application/json" '[http://localhost:9200/\_all/\_settings](http://localhost:9200/_all/_settings)' -d '{ "index": { "blocks": { "write": "false" } } }

I found this at the topic below

> [@FORBIDDEN/8/index write (api) - During date change on indexes](https://discuss.elastic.co/t/forbidden-8-index-write-api-during-date-change-on-indexes/179319/7):
>
> Nope, no prerequisite for that. I don't think either of those would cause anything related to the index being read-only. Is it possible that your node filled up with disk space and the index was marked read only because of that?

The doubt that I have is, why it happen? Because of the configuration in the warm phase, without rollover, I've setup force merge and "Timing for warm phase" 1 day from index creation.

Thanks

---

_[View the full topic](https://discuss.elastic.co/t/error-forbidden-8-index-write-api-and-elasticsearch-stop-to-receiving-logstash-bulk-requests/215028)._