# Persistent Cluster Update Settings not work

**URL:** <https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969>\
**Category:** Elasticsearch\
**Created:** [April 20, 2017, 2:39am UTC](https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969 "2017-04-20T02:39:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [April 20, 2017, 2:39am UTC](https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969/1 "2017-04-20T02:39:05Z")

</div>

Hi.

I have a question about "Cluster Update Settings" in the reference:  
[https://www.elastic.co/guide/en/elasticsearch/reference/5.3/cluster-update-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.3/cluster-update-settings.html)

I create a 2-node cluster and write some data into it. The shards of index is distributed across two nodes.  
Then I put a persistent setting to the cluster to exclude one node.

```
curl -XPUT http://1.1.1.1:18437/_cluster/settings?pretty -d '
{
  "persistent" : {
    "cluster.routing.allocation.exclude._ip": "1.1.1.1"
  }
}'

```

It doesn't work, and the shards of node 1.1.1.1 are still there and not reallocated.  
When I put the following transient setting, it works:

```
curl -XPUT http://1.1.1.1:18437/_cluster/settings?pretty -d '
{
  "transient" : {
    "cluster.routing.allocation.exclude._ip": "1.1.1.1"
  }
}'

```

I am afraid of losing my settings in case the whole cluster restart, so I want to put my settings in persistent module. why doesn't persistent cluster setting working like transient settings?

my elasticsearch version is 5.0.0

Any help would be appreciated!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 20, 2017, 7:54am UTC](https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969/2 "2017-04-20T07:54:06Z")

</div>

> [@ginger](#):
>
> I create a 2-node cluster

That is bad, please see [Important Configuration Changes | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/important-configuration-changes.html#_minimum_master_nodes)

> [@ginger](#):
>
> I am afraid of losing my settings in case the whole cluster restart, so I want to put my settings in persistent module. why doesn't persistent cluster setting working like transient settings?

What's the point of putting that in as persistent? If you want there to be no shards on that node, do a transient setting and then remove the node entirely/

---

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [April 20, 2017, 12:09pm UTC](https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969/3 "2017-04-20T12:09:08Z")

</div>

> [@warkolm](#):
>
> That is bad, please see [Important Configuration Changes | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/important-configuration-changes.html#_minimum_master_nodes)

We create a 2-node cluster just for testing. In production environment, we have more nodes.

> [@warkolm](#):
>
> What's the point of putting that in as persistent? If you want there to be no shards on that node, do a transient setting and then remove the node entirely/

I'm worrying that the setting is lost when the whole cluster restart. BTW, why persistent setting not work?

---

<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:** [May 18, 2017, 12:21pm UTC](https://discuss.elastic.co/t/persistent-cluster-update-settings-not-work/82969/4 "2017-05-18T12:21:00Z")

</div>

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