# Can't update disk space watermarks via API

**URL:** <https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793>\
**Category:** Elasticsearch\
**Created:** [September 17, 2018, 8:56am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793 "2018-09-17T08:56:07Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)\
**Post date:** [September 17, 2018, 8:56am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/1 "2018-09-17T08:56:08Z")

</div>

Hello there.  
I'm trying to update thresholds of disk space in my ES cluster but can't do this due to error.

```
[admin@client1 ~]$ curl -X PUT "10.xxx.xxx.xxx:9200/_cluster/settings?flat_settings=true" -H 'Content- 
Type: application/json' -d'
{
"transient" : {
    "cluster.routing.allocation.disk.watermark.low" : "93%"
}, "persistent" : {
    "cluster.routing.allocation.disk.watermark.low" : "93%"
}
}
'
{"error":{"root_cause":[{"type":"remote_transport_exception","reason":"[Master1][10.xxx.xxx.xxx:9300][cluster:admin/settings/update]"}],"type":"illegal_argument_exception","reason":"low disk watermark [93%] more than high disk watermark [90%]"},"status":400}

```

The problem is that high disk watermark is already set to 95%. I checked elasticsearch.yml, persistent settings and transient settings. Everywhere high watermark is 95%.  
The same problem occurs when i try to increase high watermark. It says that flood watermark is 95% but it's 98% in fact.

Where does these settings come from?

---

<div class="post-metadata">

**Author:** ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)\
**Post date:** [October 12, 2018, 8:50am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/2 "2018-10-12T08:50:31Z")

</div>

Question is still not solved ☹

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 12, 2018, 3:29pm UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/3 "2018-10-12T15:29:37Z")

</div>

Did you try to first increase `cluster.routing.allocation.disk.watermark.high` to `95%` for example?

Note that you can disable watermark with `cluster.routing.allocation.disk.threshold_enabled: false`. But this is not recommended for production clusters.

You should really have more disk space. You can do that by adding more disk, adding more nodes or cleaning non needed data.

My 2 cents.

---

<div class="post-metadata">

**Author:** ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)\
**Post date:** [October 15, 2018, 7:31am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/4 "2018-10-15T07:31:23Z")

</div>

When I try to increase disk.watermark.high it says that flood\_stage watermark (95%) is lower than new value of disk.watermark.high, but this is not true too.  
I already set flood\_stage watermark to 98%.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 15, 2018, 8:51am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/5 "2018-10-15T08:51:39Z")

</div>

Did you try the second option I gave?

---

<div class="post-metadata">

**Author:** ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)\
**Post date:** [October 15, 2018, 9:16am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/6 "2018-10-15T09:16:37Z")

</div>

Are you talking about disabling watermarks? If yes, I didn't tried it.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 15, 2018, 10:15am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/7 "2018-10-15T10:15:21Z")

</div>

Yes I do.

---

<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:** [November 12, 2018, 10:15am UTC](https://discuss.elastic.co/t/cant-update-disk-space-watermarks-via-api/148793/8 "2018-11-12T10:15:24Z")

</div>

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