# Cannot update cluster settings
**URL:** https://discuss.elastic.co/t/cannot-update-cluster-settings/121515
**Category:** Elasticsearch
**Created:** [February 26, 2018, 3:05pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515 "2018-02-26T15:05:36Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@seyhmus](https://discuss.elastic.co/u/seyhmus)
#### Post date: [February 26, 2018, 3:05pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515/1 "2018-02-26T15:05:36Z")
Hi all,
I've upgraded my cluster from 5.6 to 6.2.2 and using x-pack tls only. After upgrade cluster status is yellow and i am trying to enable routing shard allocation.
```
PUT _cluster/settings
{
"transient": {
"cluster.routing.allocation.enable": "all"
}
}
```
but recieving the following error which is not related to paremeter i am trying to change.
{
"error": {
"root\_cause": [
{
"type": "remote\_transport\_exception",
"reason": "[KLLLKELK02][10.80.43.6:9300][cluster:admin/settings/update]"
}
],
"type": "illegal\_argument\_exception",
"reason": "unknown setting [archived.cluster.routing.allocation.disk.watermark.low] did you mean any of [cluster.routing.allocation.disk.watermark.low, cluster.routing.allocation.disk.watermark.high]?"
},
"status": 400
}
I have added
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification\_mode: certificate
xpack.security.transport.ssl.key: /etc/elasticsearch/x-pack/certs/${node.name}.key
xpack.security.transport.ssl.certificate: /etc/elasticsearch/x-pack/certs/${node.name}.crt
xpack.security.transport.ssl.certificate\_authorities: ["/etc/elasticsearch/x-pack/certs/ca.crt"]
to my elasticsearch yml and GET \_cluster/health GET \_cat/allocation works well.
any ideas?
---
### Author:  [@seyhmus](https://discuss.elastic.co/u/seyhmus)
#### Post date: [February 26, 2018, 6:46pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515/2 "2018-02-26T18:46:48Z")
Solved...
> [@seyhmus](#):
>
> archived.cluster.routing.allocation.disk.watermark.low
I dont know how but "archived" was added to cluster setting, after setting archived.cluster.routing.allocation.disk.watermark.low : null i could send new settings. But still wondering how it happened.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [February 27, 2018, 1:12pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515/3 "2018-02-27T13:12:17Z")
you may have hit this one
>
---
### Author:  [@seyhmus](https://discuss.elastic.co/u/seyhmus)
#### Post date: [February 27, 2018, 1:26pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515/4 "2018-02-27T13:26:45Z")
Exactly. Thank you for informing me...
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 27, 2018, 1:26pm UTC](https://discuss.elastic.co/t/cannot-update-cluster-settings/121515/5 "2018-03-27T13:26:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.