# Automatic Write Block on Index

**URL:** <https://discuss.elastic.co/t/automatic-write-block-on-index/283014>\
**Category:** Elasticsearch\
**Created:** [September 1, 2021, 8:42am UTC](https://discuss.elastic.co/t/automatic-write-block-on-index/283014 "2021-09-01T08:42:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aamir\_Rizwan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aamir_rizwan/32/94001_2.png) [@Aamir\_Rizwan](https://discuss.elastic.co/u/Aamir_Rizwan)\
**Post date:** [September 1, 2021, 8:42am UTC](https://discuss.elastic.co/t/automatic-write-block-on-index/283014/1 "2021-09-01T08:42:58Z")

</div>

I have 3 master and 3 data nodes. I was getting this error:  
AuthorizationException(403, 'cluster\_block\_exception', 'blocked by: [FORBIDDEN/8/index write (api)];')

Increased the data nodes by 1 but still getting the same error.

Disk usage after adding a node:

```auto
shards disk.indices disk.used disk.avail disk.total disk.percent 
    11 7.2gb 8.3gb 11.2gb 19.5gb 42 x.x.x.x x.x.x.x 
    10 14.5gb 15.6gb 3.9gb 19.5gb 79 x.x.x.x x.x.x.x   
    10 7.2gb 8.3gb 11.2gb 19.5gb 42 x.x.x.x x.x.x.x  
    11 14.5gb 15.6gb 3.9gb 19.5gb 80 x.x.x.x x.x.x.x  

```

I tried updating the write block on my index to false in the settings but it become true in few seconds:

```
    "settings": {
        "index": {
            "refresh_interval": "10s",
            "number_of_shards": "3",
            "blocks": {
                "read_only": "false",
                "write": "true"
            },

```

......  
Elasticsearch version "6.2.3"

Do I need more nodes/storage?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 1, 2021, 2:32pm UTC](https://discuss.elastic.co/t/automatic-write-block-on-index/283014/2 "2021-09-01T14:32:33Z")

</div>

Any log file excerpts you might be able to share? Also, can you check with the nodes info/stats APIs how much disk space elasticsearch assumes it has.

There is a feature to block indexing if you run out of disk space, so maybe that is triggering in some way.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 1, 2021, 10:09pm UTC](https://discuss.elastic.co/t/automatic-write-block-on-index/283014/3 "2021-09-01T22:09:11Z")

</div>

Welcome to our community! 😃

> [@Aamir\_Rizwan](#):
>
> Elasticsearch version "6.2.3"

I would recommend upgrading, 6.2 is [EOL](https://www.elastic.co/support/eol) 🙂

---

<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:** [September 29, 2021, 10:09pm UTC](https://discuss.elastic.co/t/automatic-write-block-on-index/283014/4 "2021-09-29T22:09:29Z")

</div>

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