# Index logstash-\* blocked by TOO\_MANY\_REQUESTS/12/index read-only

**URL:** <https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690>\
**Category:** Logstash\
**Created:** [July 27, 2020, 6:27am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690 "2020-07-27T06:27:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mozhganch](https://avatars.discourse-cdn.com/v4/letter/m/e47c2d/32.png) [@Mozhganch](https://discuss.elastic.co/u/Mozhganch)\
**Post date:** [July 27, 2020, 6:27am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/1 "2020-07-27T06:27:06Z")

</div>

Hi  
my logstash service starts without error but it stops with this error "Failed with result 'exit-code'"

then I run it without logstash service.  
so after sending 5 entry point, the following error is occured:

[INFO] 2020-07-27 10:41:09.254 [[main]\>worker2] elasticsearch - retrying failed action with response code: 429 ({"type"=\>"cluster\_block\_exception", "reason"=\>"index [logstash-2020.07.27] blocked by: [TOO\_MANY\_REQUESTS/12/index read-only / allow delete (api)];"})  
[INFO] 2020-07-27 10:41:09.255 [[main]\>worker2] elasticsearch - Retrying individual bulk actions that failed or were rejected by the previous bulk request. {:count=\>1}

I try these solutions but it doesn't work for me:

PUT \_settings  
{  
"index": {  
"blocks": {  
"read\_only\_allow\_delete": "false"  
}  
}  
}

PUT logstash-2020.07.27/\_settings  
{  
"index": {  
"blocks": {  
"read\_only\_allow\_delete": "false"  
}  
}  
}

After deleting index, just 3 or 4 entry points can be add to index but others entry points fetch above error!  
Any one can help me?

---

<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:** [July 27, 2020, 8:01am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/2 "2020-07-27T08:01:19Z")

</div>

What version are you running?  
What is the output from `_cat/nodes?v` and `_cat/indices?v`?

Please format your code/logs/config using the `</>` button, or markdown style back ticks. It helps to make things easy to read which helps us help you 🙂

---

<div class="post-metadata">

**Author:** ![Mozhganch](https://avatars.discourse-cdn.com/v4/letter/m/e47c2d/32.png) [@Mozhganch](https://discuss.elastic.co/u/Mozhganch)\
**Post date:** [July 27, 2020, 8:21am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/3 "2020-07-27T08:21:17Z")

</div>

run code on version 7.8.0  
result for running _cat/indices is:  
yellow open elastalert\_stat\_status iOOTNQGEQBq8bBSSSoNQyA 1 1 6 0 29.5kb 29.5kb  
yellow open elastalert\_status\_status 26KgVzZYRjuGDt4E_-yiBQ 1 1 316 0 84.6kb 84.6kb  
yellow open elastalert\_status OFWCLY9FSvykESzsDvFodQ 1 1 14 0 32.7kb 32.7kb  
yellow open elastalert\_status\_past 8VD63-WNTgaMHiLv\_aza7A 1 1 0 0 208b 208b  
green open .apm-agent-configuration e\_kurIzPQp-jGMuKXgRlNg 1 0 0 0 208b 208b  
yellow open elastalert\_status\_silence Yv-Se1rzSVS\_9Ga9Xd3CIA 1 1 0 0 208b 208b  
green open .kibana\_1 BzA68BuVQBGa5CmVBd-R6w 1 0 129 9 119.5kb 119.5kb  
green open .kibana-event-log-7.8.0-000001 tysDNrARSbmFsI3nC\_q0aA 1 0 8 0 40.9kb 40.9kb  
green open .apm-custom-link u8Tsm5ofRH6UI6iR7Ko3mQ 1 0 0 0 208b 208b  
yellow open logstashtest RRK-IjU0Q929BFnZi7LA\_w 1 1 1 0 5.1kb 5.1kb  
green open .kibana\_task\_manager\_1 NoaSsieASfOHmECNWed5Hg 1 0 5 8 67kb 67kb  
yellow open logstash-test KClvmfynTQCa9fHLzroYhQ 1 1 13 0 35.1kb 35.1kb  
yellow open logstash-2020.07.27 xiocNGiHQbekCKdx38owNA 1 1 3 0 8.9kb 8.9kb  
yellow open elastalert\_stat\_error -NfeNANeT0K5H4liVBB4xg 1 1 1 0 10.4kb 10.4kb  
yellow open elastalert\_status\_error afCFFG6JRwy82oz\_YgbK0A 1 1 5 0 29.8kb 29.8kb  
yellow open customer rb3uuSK0TseWp90yG6nimQ 1 1 1 0 3.5kb 3.5kb

also result for running \_cat/nodes is:

127.0.0.1 17 97 14 0.72 0.68 0.55 dilmrt \* mypc-Compaq-Elite-8300-SFF

my logstash config also is:  
input { stdin { } }

output {  
elasticsearch {  
hosts =\> ["localhost:9200"]  
index =\> "logstash-%{+YYYY.MM.dd}"  
}  
stdout { codec =\> rubydebug }  
}

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![Mozhganch](https://avatars.discourse-cdn.com/v4/letter/m/e47c2d/32.png) [@Mozhganch](https://discuss.elastic.co/u/Mozhganch)\
**Post date:** [July 28, 2020, 5:14am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/4 "2020-07-28T05:14:35Z")

</div>

less capacity of hard disc is the main problem and solve this by adding following line to elasticsearch.yaml  
cluster.routing.allocation.disk.threshold\_enabled:false  
to use the hard if even more than 95% disc is full.

---

<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:** [July 28, 2020, 5:16am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/5 "2020-07-28T05:16:42Z")

</div>

You are likely to run into bigger issues with that, as Elasticsearch will completely stop if there is no disk space available.

---

<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:** [August 25, 2020, 5:18am UTC](https://discuss.elastic.co/t/index-logstash-blocked-by-too-many-requests-12-index-read-only/242690/6 "2020-08-25T05:18:19Z")

</div>

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