# Issue on updating index\_pattern using api

**URL:** <https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924>\
**Category:** Metrics\
**Created:** [June 12, 2020, 4:57pm UTC](https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924 "2020-06-12T16:57:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![snolfi](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@snolfi](https://discuss.elastic.co/u/snolfi)\
**Post date:** [June 12, 2020, 4:57pm UTC](https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924/1 "2020-06-12T16:57:42Z")

</div>

Hello,

i'm having a big issue in updating index\_pattern using api. My index\_patterns have the following property:

> "index": {  
> "blocks": {  
> "read\_only\_allow\_delete": "true"  
> }  
> }

In this way, by kibana console, i don't see the related metrics:

![image](https://us1.discourse-cdn.com/elastic/original/3X/5/c/5c7d6abed6920c3152f75ce7ba8329c073ccc4c2.png)

So, in order to solve this, i used this curl command:

> curl -X PUT "[http://localhost:9200/\*/\_settings](http://localhost:9200/*/_settings)" -H 'Content-Type: application/json' -d'{  
> "index": {  
> "blocks": {  
> "read\_only\_allow\_delete": "false"  
> }  
> }  
> }'

This command worked but what's happening now is that, after a few times, this property comes back to its original value ("true"), bringing back my initial issue.

Could somebody help me in understanding what's happening and how can i solve this?

An another important aspect is that my index-patterns were imported on kibana using api (i have much of them exported by another environment and it's not thinkable creating all of them manually).

Thanks in advance to everybody who will help me  
KR  
Simone

---

<div class="post-metadata">

**Author:** ![Zacqary](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zacqary/32/60839_2.png) [@Zacqary](https://discuss.elastic.co/u/Zacqary)\
**Post date:** [July 2, 2020, 4:46pm UTC](https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924/2 "2020-07-02T16:46:19Z")

</div>

Sorry for the long wait in getting back to you on this!

The read-only property could be appearing because of Elasticsearch's storage space circuit breaker. Can you check your Elasticsearch logs and see if you've been getting any warnings about storage space? If that's happening, then increasing the storage capacity of your node may fix the issue.

Let me know if that works. If not we can dig deeper.

---

<div class="post-metadata">

**Author:** ![snolfi](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@snolfi](https://discuss.elastic.co/u/snolfi)\
**Post date:** [July 29, 2020, 1:07pm UTC](https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924/3 "2020-07-29T13:07:10Z")

</div>

Hello @Zacqary, i was sure to have answered, sorry

Anyway it was as you said, after cleaning the fs ES came back to work as expected

Regards  
Simone

---

<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 26, 2020, 1:07pm UTC](https://discuss.elastic.co/t/issue-on-updating-index-pattern-using-api/236924/4 "2020-08-26T13:07:10Z")

</div>

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