# Elasticsearch deprecation issues **URL:** \ **Category:** Elasticsearch\ **Created:** [February 15, 2023, 5:47am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543 "2023-02-15T05:47:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\ **Post date:** [February 15, 2023, 5:47am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/1 "2023-02-15T05:47:51Z")
I can't upgrade to 8.6.1 due to a deprecation issue. I can't update the elasticsearch.yml, because I have a cloud solution. Problem: setting [cluster.routing.allocation.disk.watermark.enable\_for\_single\_data\_node] is deprecated and will not be available in a future version How do I get rid of this issue? Thanks, Herman ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [February 15, 2023, 1:02pm UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/2 "2023-02-15T13:02:16Z")
> [@hermlam](#): > > cluster.routing.allocation.disk.watermark.enable\_for\_single\_data\_node Hi @hermlam, [Looking at the docs, this value will default to true](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/migrating-8.0.html). There is some guidance on what to do if you need the previous false behaviour: > If the old behavior is desired for a single data node cluster, disk based allocation can be disabled by setting `cluster.routing.allocation.disk.threshold_enabled: false` Hope that helps! ---
**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\ **Post date:** [March 1, 2023, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/3 "2023-03-01T07:25:52Z")
Hi Carly, Thanks for your answer. I am having a problem setting this: `Preformatted text`PUT \_cluster/settings { "transient": { "cluster.routing.allocation.disk.threshold\_enabled": false } } `Preformatted text` Error: { "error": { "root\_cause": [ { "type": "security\_exception", "reason": "Operator privileges are required for setting [cluster.routing.allocation.disk.threshold\_enabled]" } ], "type": "security\_exception", "reason": "action [cluster:admin/settings/update] is unauthorized for user [692420039] with assigned roles [superuser] because it requires operator privileges, this action is granted by the cluster privileges [manage,all]", "caused\_by": { "type": "security\_exception", "reason": "Operator privileges are required for setting [cluster.routing.allocation.disk.threshold\_enabled]" } }, "status": 403 } I am running in a Elastic Cloud environment ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [March 1, 2023, 10:08am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/4 "2023-03-01T10:08:16Z")
Ok, that looks like you don't have permissions to set that value. I have found another thread in Slack with users having the same issue, where guidance is given to ignore the error for a minor upgrade: Original question: [Slack](https://elasticstack.slack.com/archives/C017Y6PQZ0D/p1674828824293829) Response: [Slack](https://elasticstack.slack.com/archives/C017Y6PQZ0D/p1675080974747429) Have a look at the thread and see if that option works for you and if this value changing does have an impact on your usage. Otherwise, you'll need to look at your privileges if you definitely need to change this setting. ---
**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\ **Post date:** [March 4, 2023, 1:15pm UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/5 "2023-03-04T13:15:40Z")
Hi Carly, I can't find these topics at Slack. And this would be a temporarely solution? What when the time comes for a major upgrade? Elevating my privilige rights? No idea how to do this in the Elastic Cloud. So I am a little bit stuck here. Thanks for helping, Herman ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [March 6, 2023, 11:20am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/6 "2023-03-06T11:20:40Z")
Hi @hermlam, So by elevating your privileges, I'm referring to the Roles screen in Stack Management where additional roles can be added to your user. I see the messages on Slack are no longer available. But the guidance in the thread, as mentioned above, was ignoring for minor upgrade. Major upgrade wasn't mentioned, but I would go with the [migration guide guidance](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/migrating-8.0.html) mentioned previously. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 3, 2023, 11:20am UTC](https://discuss.elastic.co/t/elasticsearch-deprecation-issues/325543/7 "2023-04-03T11:20:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.