# Cluster.routing.allocation.exclude.\_name stops working \[ES6.1.2\]

**URL:** <https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705>\
**Category:** Elasticsearch\
**Created:** [January 30, 2018, 9:25pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705 "2018-01-30T21:25:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [January 30, 2018, 9:25pm UTC](https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705/1 "2018-01-30T21:25:28Z")

</div>

I'm migrating shards from some old nodes to some new nodes. I excluded the old nodes as follows:

```auto
PUT /_cluster/settings?pretty
{
  "transient": {
    "cluster.routing.allocation.exclude._name": "node-1,node-2,node-3,node-4,node-5,node-6,node-7,node-8,node-9"
  }
}

```

Halfway through, I noticed a config problem on one of the new nodes so I stopped rebalancing as follows:

```auto
PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.cluster_concurrent_rebalance": 0
  }
}

```

After fixing the node's config (it was not a master node) and restarting it, I re-enabled rebalancing:

```auto
PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.cluster_concurrent_rebalance": -1
  }
}

```

Well, rebalancing started up, but the exclude list was ignored. Shards got equally distributed among old and new nodes. I verified the transient cluster setting was still in place with

```auto
GET _cluster/settings

```

I re-sent the `cluster.routing.allocation.exclude._name` cluster setting to no avail. Then I set it to the empty string "" and then re-sent in the "node-1,node-2,node-3,node-4,node-5,node-6,node-7,node-8,node-9" list. This worked!

I'm glad that this worked, but it didn't work as I expected. Did I go about this the wrong way?

---

<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:** [February 2, 2018, 3:45am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705/2 "2018-02-02T03:45:42Z")

</div>

What version did you try this on?

---

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [February 2, 2018, 5:58am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705/3 "2018-02-02T05:58:41Z")

</div>

6.1.2

---

<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:** [March 2, 2018, 5:58am UTC](https://discuss.elastic.co/t/cluster-routing-allocation-exclude-name-stops-working-es6-1-2/117705/4 "2018-03-02T05:58:50Z")

</div>

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