# Index read-only after upgrading to 7.0

**URL:** <https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387>\
**Category:** Elasticsearch\
**Created:** [April 11, 2019, 11:17am UTC](https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387 "2019-04-11T11:17:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![epacke](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/epacke/32/40517_2.png) [@epacke](https://discuss.elastic.co/u/epacke)\
**Post date:** [April 11, 2019, 11:17am UTC](https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387/1 "2019-04-11T11:17:59Z")

</div>

Hi!  
Saw that ELK 7.0 was available and upgraded my lab. After that I got these errors from logstash:

`Apr 11 13:01:38 linuxmgmt.j.local logstash[29896]: [2019-04-11T13:01:38,243][INFO][logstash.outputs.elasticsearch] retrying failed action with response code: 403 ({"type"=>"cluster_block_exception", "reason"=>"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"})`

I've tried to run `PUT /_all/_settings {"index.blocks.read_only_allow_delete": null}` and then it works for a minute or two. Then it's back to the original issue.

I've seen other articles where the person was running out of disk but in this case I've got disk space available.

Anyone else seen this issue?

Kind regards,  
Patrik

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 11, 2019, 11:27am UTC](https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387/2 "2019-04-11T11:27:03Z")

</div>

This block is applied when running out of disk space indeed, and that's the only circumstances under which it is automatically applied.

There will be messages in the server log giving details of how Elasticsearch arrived at this decision. Look for messages from a logger called `DiskThresholdMonitor`.

---

<div class="post-metadata">

**Author:** ![epacke](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/epacke/32/40517_2.png) [@epacke](https://discuss.elastic.co/u/epacke)\
**Post date:** [April 21, 2019, 12:14pm UTC](https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387/3 "2019-04-21T12:14:27Z")

</div>

Thanks David. I deleted a few days of data and everything started to work again.

Kind regards,  
Patrik

---

<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:** [May 19, 2019, 12:14pm UTC](https://discuss.elastic.co/t/index-read-only-after-upgrading-to-7-0/176387/4 "2019-05-19T12:14:30Z")

</div>

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