# ELK 6.3.1 - how to delete \_cluster/settings **URL:** \ **Category:** Elasticsearch\ **Created:** [July 26, 2018, 2:33pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795 "2018-07-26T14:33:21Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 26, 2018, 2:33pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/1 "2018-07-26T14:33:22Z")
Hello, I am facing issue with updating cluster settings in ES 6.3.1 I tried below command ## PUT \_cluster/settings { "transient": { "cluster.routing.allocation.disk.watermark.low": "100gb", "cluster.routing.allocation.disk.watermark.high": "50gb", "cluster.info.update.interval": "1m" } } ## Output { "error": { "root\_cause": [ { "type": "remote\_transport\_exception", "reason": "[elk-mgm-node3][10.138.0.8:9300][cluster:admin/settings/update]" } ], "type": "illegal\_argument\_exception", "reason": "unable to consistently parse [cluster.routing.allocation.disk.watermark.low=100gb], [cluster.routing.allocation.disk.watermark.high=50gb], and [cluster.routing.allocation.disk.watermark.flood\_stage=95%] as percentage or bytes", "caused\_by": { "type": "parse\_exception", "reason": "failed to parse setting [cluster.routing.allocation.disk.watermark.flood\_stage] with value [95%] as a size in bytes: unit is missing or unrecognized" } }, "status": 400 } ## Current cluster settings are as below { "persistent": { "archived": { "indices": { "store": { "throttle": { "max\_bytes\_per\_sec": "10gb" } } } }, "cluster": { "routing": { "allocation": { "node\_concurrent\_recoveries": "8" } } } }, "transient": { "archived": { "cluster": { "routing": { "allocation": { "disk": { "watermark": { "low": "100gb", "high": "50gb" } } } } } }, "cluster": { "routing": { "allocation": { "disk": { "watermark": { "low": "100gb", "flood\_stage": "10gb", "high": "50gb" } }, "enable": "all" } }, "info": { "update": { "interval": "1m" } } } } } Is there any way to delete these settings 1. Related issue When I try to turn on monitoring in ELK 6.3.1 I get below error on UI 400 Bad Request [remote\_transport\_exception] [elk-mgm-node3][10.138.0.8:9300][cluster:admin/settings/update] (Recently upgraded ELK from 5.6 to 6.3) ---
**Author:** ![pastechecker](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pastechecker](https://discuss.elastic.co/u/pastechecker)\ **Post date:** [July 26, 2018, 2:36pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/2 "2018-07-26T14:36:28Z")
what is yous elasticsearch.yml ? ---
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 26, 2018, 2:37pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/3 "2018-07-26T14:37:39Z")
elasticsearch.yml from management node ? ---
**Author:** ![pastechecker](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pastechecker](https://discuss.elastic.co/u/pastechecker)\ **Post date:** [July 26, 2018, 2:38pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/4 "2018-07-26T14:38:00Z")
Yes. ---
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 26, 2018, 2:41pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/5 "2018-07-26T14:41:47Z")
# ======================== Elasticsearch Configuration ========================= # # NOTE: Elasticsearch comes with reasonable defaults for most settings. # Before you set out to tweak and tune the configuration, make sure you # understand what are you trying to accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please see the documentation for further information on configuration options: # [http://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html) # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # cluster.name: cluster\_name # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # node.name: elk-mgm-node # # Add custom attributes to the node: # # node.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # path.data: path # # Path to log files: # # path.logs: /path/to/logs # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.mlockall: true bootstrap.memory\_lock: true bootstrap.system\_call\_filter: false # # Make sure that the `ES_HEAP_SIZE` environment variable is set to about half the memory # available on the system and that the owner of the process is allowed to use this limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # Set the bind address to a specific IP (IPv4 or IPv6): # network.bind\_host: 0.0.0.0 # # Set a custom port for HTTP: # #net.publish\_host: ip network.host: ip http.port: 9200 # # For more information, see the documentation at: # [http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html) # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when new node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # # discovery.zen.ping.unicast.hosts: ["host1", "host2"] # # Prevent the "split brain" by configuring the majority of nodes (total number of nodes / 2 + 1): # # discovery.zen.minimum\_master\_nodes: 3 # # For more information, see the documentation at: # [http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery.html) # # ---------------------------------- Gateway ----------------------------------- # # Block initial recovery after a full cluster restart until N nodes are started: # # gateway.recover\_after\_nodes: 3 # # For more information, see the documentation at: # [http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-gateway.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-gateway.html) # # ---------------------------------- Various ----------------------------------- # # Disable starting multiple nodes on a single system: # # node.max\_local\_storage\_nodes: 1 # # Require explicit names when deleting indices: # # action.destructive\_requires\_name: true discovery.zen.minimum\_master\_nodes: 2 #discovery.zen.ping.timeout: 120s discovery.zen.ping\_timeout: 120s #discovery.zen.ping.multicast.enabled: true discovery.zen.ping.unicast.hosts: ["ip\_list"] node.master: true node.data: false #gateway.recover\_after\_nodes: 8 #gateway.expected\_nodes: 10 #gateway.recover\_after\_time: 5m ---
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 26, 2018, 3:21pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/6 "2018-07-26T15:21:16Z")
@pastechecker is there any direct way to force cluster settings ? Due to this I am not able to change routing as well PUT /\_cluster/settings { "transient": { "cluster.routing.allocation.enable": "all" }} * * * ## Output { "error": { "root\_cause": [ { "type": "remote\_transport\_exception", "reason": "[elk-mgm-node3][10.138.0.8:9300][cluster:admin/settings/update]" } ], "type": "illegal\_argument\_exception", "reason": "unknown setting [archived.cluster.routing.allocation.disk.watermark.high] did you mean any of [cluster.routing.allocation.disk.watermark.high, cluster.routing.allocation.disk.watermark.low]?", "suppressed": [ { "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 } ---
**Author:** ![pastechecker](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pastechecker](https://discuss.elastic.co/u/pastechecker)\ **Post date:** [July 27, 2018, 11:40am UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/7 "2018-07-27T11:40:56Z")
I cannot help you, that is beyond my current understanding and my experience. You need to go deeper into upgrade process between versions. ---
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 27, 2018, 11:47am UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/8 "2018-07-27T11:47:33Z")
Hey, No problem. Thanks a lot. I know one way is to delete global\_state file and take full cluster restart on each node But I am searching for "api" way to change these settings @elastic Hello, it would be a great help if I get some clue on this ! ---
**Author:** ![Harshad\_Velapure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshad_velapure/32/33684_2.png) [@Harshad\_Velapure](https://discuss.elastic.co/u/Harshad_Velapure)\ **Post date:** [July 29, 2018, 8:23pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/9 "2018-07-29T20:23:43Z")
I solved it, put to null state all the settings that are showing in archived. ---
**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, 2018, 8:23pm UTC](https://discuss.elastic.co/t/elk-6-3-1-how-to-delete-cluster-settings/141795/10 "2018-08-26T20:23:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.