# Locked/read only indices **URL:** \ **Category:** Elasticsearch\ **Created:** [August 17, 2018, 8:14am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850 "2018-08-17T08:14:55Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![nkaenzig](https://avatars.discourse-cdn.com/v4/letter/n/97f17d/32.png) [@nkaenzig](https://discuss.elastic.co/u/nkaenzig)\ **Post date:** [August 17, 2018, 8:14am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/1 "2018-08-17T08:14:55Z")
When I try to change my visualizations in Kibana I get the following message: Visualization Editor: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster\_block\_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; So somehow my indices got locked. I allready tried out the proposed solution in the following post, which unfortunately doesn't work for me: > [@FORBIDDEN/12/index read-only / allow delete (api)\]](https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/110282): > > I am running logstash on windows 2016 vm . I use it from administrator command line. I keep getting this message. It won't let me save my visualization on kibana and keeps me from shutting it down (ctrl+c). This is the message: 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)] My elasticsearch is operating using default configuration. I asked on logstash… Do you have another idea what I could try to unlock the indexes again? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 17, 2018, 8:19am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/2 "2018-08-17T08:19:01Z")
This often means that you are running out of disk space and have passed one of the high watermark thresholds. Unless you correct this indices will go back into read-only state. ---
**Author:** ![nkaenzig](https://avatars.discourse-cdn.com/v4/letter/n/97f17d/32.png) [@nkaenzig](https://discuss.elastic.co/u/nkaenzig)\ **Post date:** [August 17, 2018, 8:37am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/3 "2018-08-17T08:37:52Z")
Thanks for the quick response. On the partition I am storing my indexes there is still over 200GB of disk space left. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 17, 2018, 8:42am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/4 "2018-08-17T08:42:29Z")
How big is the partition? The threshold is by default specified as a percentage. ---
**Author:** ![nkaenzig](https://avatars.discourse-cdn.com/v4/letter/n/97f17d/32.png) [@nkaenzig](https://discuss.elastic.co/u/nkaenzig)\ **Post date:** [August 17, 2018, 8:43am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/5 "2018-08-17T08:43:52Z")
The partition is 5 Terrabyte in size. Is there away to change the threshold or even deactivate it? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 17, 2018, 8:49am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/6 "2018-08-17T08:49:39Z")
Yes, you can change it. Be sure it does not make you run out of disk space though as that can cause corruption. Look for watermark in the docs. ---
**Author:** ![nkaenzig](https://avatars.discourse-cdn.com/v4/letter/n/97f17d/32.png) [@nkaenzig](https://discuss.elastic.co/u/nkaenzig)\ **Post date:** [August 17, 2018, 8:59am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/7 "2018-08-17T08:59:30Z")
Thank you so much for your help. I ran the following command to disable the threshold: > PUT /\_cluster/settings > { > "persistent" : { > "cluster.routing.allocation.disk.threshold\_enabled" : false > } > } After that I restarted the elasticsearch and Kibana services, ran the following command: > PUT .kibana/\_settings > { > "index": { > "blocks": { > "read\_only\_allow\_delete": false > } > } > } Now it works again. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 17, 2018, 9:02am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/8 "2018-08-17T09:02:54Z")
Be careful with that though as you could run into serious problems now that you have disabled this safety check. There is a good reason it is there by default... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 14, 2018, 9:02am UTC](https://discuss.elastic.co/t/locked-read-only-indices/144850/9 "2018-09-14T09:02:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.