# How to remove stuck persistent setting after upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [December 27, 2017, 9:30pm UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366 "2017-12-27T21:30:01Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Jacket](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@Jacket](https://discuss.elastic.co/u/Jacket)\ **Post date:** [December 27, 2017, 9:30pm UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/1 "2017-12-27T21:30:01Z")
I have just upgraded my cluster from `5.6` to `6.1`. I did a rolling upgrade as the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) specified. It looks like a setting that I was using isn't available anymore in 6.1. That would've been fine, but now I can't even enable my shard allocation, so now my last node won't allocate its shards. Doing something as simple as this: ``` curl -XPUT 'localhost:9200/_cluster/settings?pretty' -H 'Content-Type: application/json' -d' { "persistent" : { "cluster.routing.allocation.enable" : "all" } } ``` results in this: ``` { "error" : { "root_cause" : [ { "type" : "remote_transport_exception", "reason" : "[inoreader-es4][92.247.179.253:9300][cluster:admin/settings/update]" } ], "type" : "illegal_argument_exception", "reason" : "unknown setting [indices.store.throttle.max_bytes_per_sec] did you mean [indices.recovery.max_bytes_per_sec]?" }, "status" : 400 } ``` No matter what setting I try to change I always get this error. Yes, I did set `indices.store.throttle.max_bytes_per_sec` as persistent setting once in 5.x, and I'm OK with having to set it to a new name now, but how can I even remove it? It's not in `elasticsearch.yml`. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [December 28, 2017, 7:51am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/2 "2017-12-28T07:51:06Z")
> [@Jacket](#): > > indices.store.throttle.max\_bytes\_per\_sec as i know this is delete in es 6 > **[Settings changes | Elasticsearch Reference \[6.0\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/breaking_60_settings_changes.html#_store_throttling_settings)** ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [December 28, 2017, 7:51am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/3 "2017-12-28T07:51:55Z")
set: **"indices.store.throttle.max\_bytes\_per\_sec": null** remove it. ---
**Author:** ![Jacket](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@Jacket](https://discuss.elastic.co/u/Jacket)\ **Post date:** [December 30, 2017, 11:38pm UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/4 "2017-12-30T23:38:47Z")
I've tried that already. It raises the same error. In fact ANY setting that I try to PUT raises the same error `unknown setting [indices.store.throttle.max_bytes_per_sec] did you mean [indices.recovery.max_bytes_per_sec]?`. I can't seem to find a way to remove it via the APIs. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [January 2, 2018, 6:58am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/5 "2018-01-02T06:58:50Z")
show your put curl.. ---
**Author:** ![a5a](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@a5a](https://discuss.elastic.co/u/a5a)\ **Post date:** [January 3, 2018, 4:05am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/7 "2018-01-03T04:05:03Z")
@jacket can you try `PUT _cluster/settings { "persistent": { "indices.store.throttle.*": null } }`? I'm not sure why it doesn't let you set that specific setting to null, but try removing everything under throttle, see if that works. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [January 3, 2018, 6:13am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/8 "2018-01-03T06:13:47Z")
it know in 6.x? or in 5.x ? if 5.x use this. > [@a5a](#): > > { "indices.store.throttle.\*": null } }? as i know not use \* use "indices.store.throttle.max\_bytes\_per\_sec": null ---
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [January 3, 2018, 6:19am UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/9 "2018-01-03T06:19:52Z")
How about using an empty string `""` instead of `null` Same result? ---
**Author:** ![a5a](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@a5a](https://discuss.elastic.co/u/a5a)\ **Post date:** [January 3, 2018, 4:26pm UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/10 "2018-01-03T16:26:36Z")
Yes, that should work in 5.x and 6.x. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 31, 2018, 4:26pm UTC](https://discuss.elastic.co/t/how-to-remove-stuck-persistent-setting-after-upgrade/113366/11 "2018-01-31T16:26:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.