# Routing.allocation.exclude.tag: Node level index settings not getting picked up by new indexes **URL:** \ **Category:** Elasticsearch\ **Created:** [August 22, 2013, 6:45am UTC](https://discuss.elastic.co/t/routing-allocation-exclude-tag-node-level-index-settings-not-getting-picked-up-by-new-indexes/13293 "2013-08-22T06:45:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![tgillies](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@tgillies](https://discuss.elastic.co/u/tgillies)\ **Post date:** [August 22, 2013, 6:45am UTC](https://discuss.elastic.co/t/routing-allocation-exclude-tag-node-level-index-settings-not-getting-picked-up-by-new-indexes/13293/1 "2013-08-22T06:45:55Z")
Hi, I have a 4 node ES cluster. I am attempting to use the index.routing.allocation.exclude.tag tag so that, unless otherwise stated, indexes will only be replicated to 3 of our 4 nodes. (The 'replica' setting in the elasticsearch.yml file is set to '2' on all nodes in the cluster). (Eventually the plan is that some very specific indexes will be replicated onto all 4 nodes of the cluster). I have tagged the 'unwanted' node with the "dr" tag in it's elasticsearch.yml. _Step 1: Updated routing.allocation.exclude.tag in existing indexes_ I then updated all of my existing indexes to never replicate to the 'DR' node using the below curl command: curl -XPUT ssp-search:9200/\_settings -d '{ "index" : { "routing.allocation.exclude.tag" : "DR" } }' This works perfectly. None of my existing indexes are ever replicated to the "DR" node in the cluster. \*Step 2: Changed \*\*routing.allocation.exclude.tag in elasticsearch.yml \*_so that this setting doesn't need to be set when creating a new index_ I decided I would set the routing.allocation.exclude.tag setting in the elasticsearch.yml file on all four nodes, so that all new indexes that are created will not replicate to the dr node by default. However, when I create a new index (without setting the routing.allocation.exclude.tag at the index level), shards are still replicating to the "dr" node. This confuses me as my understanding is that index level settings set at the node level should be inherited by the index, and only overrridden if I explicitly set something different at the index level. [http://www.elasticsearch.org/guide/reference/setup/configuration/](http://www.elasticsearch.org/guide/reference/setup/configuration/) My elasticsearch.yml contains (among other things) the following: ## # Stop indexes automatically allocating to bne2repl2 ## index.routing.allocation.exclude.tag: dr _I have also tried putting the tag in double quotes:_ ## # Stop indexes automatically allocating to bne2repl2 ## index.routing.allocation.exclude.tag: "dr" All nodes in the index have been restarted MULTIPLE times. Other index settings that are set in the elasticsearch.yml are working fine (for example, new indexes are created with 2 replicas, as per the setting in my elasticsearch.yml. Has anybody seen this issue before, or have any ideas or suggestions? Hopefully I have just somehow stuffed up the syntax, or my understanding of how the settings are inherited is flawed. Any help or ideas would be much appreciated -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:20am UTC](https://discuss.elastic.co/t/routing-allocation-exclude-tag-node-level-index-settings-not-getting-picked-up-by-new-indexes/13293/2 "2017-07-06T02:20:15Z")