# Setting index.routing.allocation.include.node failure

**URL:** <https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881>\
**Category:** Elasticsearch\
**Created:** [April 9, 2014, 12:46am UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881 "2014-04-09T00:46:29Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Bellows](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Ryan\_Bellows](https://discuss.elastic.co/u/Ryan_Bellows)\
**Post date:** [April 9, 2014, 12:46am UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/1 "2014-04-09T00:46:29Z")

</div>

Hi all,  
I've got a 5 node elasticsearch cluster that has 3 machines with a  
"node.storage: ssd\_fast" and 2 with "node.storage: sata\_slow" attributes.  
I'd like to write today's index (this is being used for logstash) to the  
ssd machines, and then use the slow ones for archiving shards.

Here's the error I"m getting when I try to change the index routing (for  
all existing indexes):

curl -XPUT es3:9200/\_settings -d '{  
"index" : {  
"index.routing.allocation.include.node.storage" : "ssd\_fast"  
}  
}'

{"error":"RemoteTransportException[[es3][inet[/10.123.123.103:9300]][indices/settings/update]];  
nested: ElasticsearchIllegalArgumentException[Can't update non dynamic  
settings[[index.index.routing.allocation.include.node.storage]] for open  
indices[[logstash-sfo1-2014.04.09, logstash-sfo1-2014.04.08, kibana-int]]];  
","status":400}k

Any pointers appreciated, thanks.

-Ryan

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 9, 2014, 12:53am UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/2 "2014-04-09T00:53:43Z")

</div>

You need to put that into the elasticsearch.yml and then restart each node.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 9 April 2014 10:46, Ryan Bellows [rtb@weebly.com](mailto:rtb@weebly.com) wrote:

> Hi all,  
> I've got a 5 node elasticsearch cluster that has 3 machines with a  
> "node.storage: ssd\_fast" and 2 with "node.storage: sata\_slow" attributes.  
> I'd like to write today's index (this is being used for logstash) to the  
> ssd machines, and then use the slow ones for archiving shards.
> 
> Here's the error I"m getting when I try to change the index routing (for  
> all existing indexes):
> 
> curl -XPUT es3:9200/\_settings -d '{  
> "index" : {  
> "index.routing.allocation.include.node.storage" : "ssd\_fast"  
> }  
> }'
> 
> {"error":"RemoteTransportException[[es3][inet[/10.123.123.103:9300]][indices/settings/update]];  
> nested: ElasticsearchIllegalArgumentException[Can't update non dynamic  
> settings[[index.index.routing.allocation.include.node.storage]] for open  
> indices[[logstash-sfo1-2014.04.09, logstash-sfo1-2014.04.08, kibana-int]]];  
> ","status":400}k
> 
> Any pointers appreciated, thanks.
> 
> -Ryan
> 
> --  
> 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).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624b4jV5LqDUkBYUeBz9\_TOvOG\_9uxY8MigOOv1tRCxjfFA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624b4jV5LqDUkBYUeBz9_TOvOG_9uxY8MigOOv1tRCxjfFA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ryan\_Bellows](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Ryan\_Bellows](https://discuss.elastic.co/u/Ryan_Bellows)\
**Post date:** [April 9, 2014, 12:59am UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/3 "2014-04-09T00:59:33Z")

</div>

Ah, to be clear, those attributes are already in the elasticsearch.yml  
files on all 5 servers.

On Tuesday, April 8, 2014 5:53:43 PM UTC-7, Mark Walkom wrote:

> You need to put that into the elasticsearch.yml and then restart each node.
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \<javascript:\>  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 9 April 2014 10:46, Ryan Bellows \<[r...@weebly.com](mailto:r...@weebly.com) \<javascript:\>\> wrote:
> 
> > Hi all,  
> > I've got a 5 node elasticsearch cluster that has 3 machines with a  
> > "node.storage: ssd\_fast" and 2 with "node.storage: sata\_slow" attributes.  
> > I'd like to write today's index (this is being used for logstash) to the  
> > ssd machines, and then use the slow ones for archiving shards.
> > 
> > Here's the error I"m getting when I try to change the index routing (for  
> > all existing indexes):
> > 
> > curl -XPUT es3:9200/\_settings -d '{  
> > "index" : {  
> > "index.routing.allocation.include.node.storage" : "ssd\_fast"  
> > }  
> > }'
> > 
> > {"error":"RemoteTransportException[[es3][inet[/10.123.123.103:9300]][indices/settings/update]];  
> > nested: ElasticsearchIllegalArgumentException[Can't update non dynamic  
> > settings[[index.index.routing.allocation.include.node.storage]] for open  
> > indices[[logstash-sfo1-2014.04.09, logstash-sfo1-2014.04.08, kibana-int]]];  
> > ","status":400}k
> > 
> > Any pointers appreciated, thanks.
> > 
> > -Ryan
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 9, 2014, 1:01am UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/4 "2014-04-09T01:01:24Z")

</div>

Ok, but you can't dynamically update them, you can only ever define them in  
the .yml and then restart the service for the value to be changed.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 9 April 2014 10:59, Ryan Bellows [rtb@weebly.com](mailto:rtb@weebly.com) wrote:

> Ah, to be clear, those attributes are already in the elasticsearch.yml  
> files on all 5 servers.
> 
> On Tuesday, April 8, 2014 5:53:43 PM UTC-7, Mark Walkom wrote:
> 
> > You need to put that into the elasticsearch.yml and then restart each  
> > node.
> > 
> > Regards,  
> > Mark Walkom
> > 
> > Infrastructure Engineer  
> > Campaign Monitor  
> > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com)  
> > web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> > 
> > On 9 April 2014 10:46, Ryan Bellows [r...@weebly.com](mailto:r...@weebly.com) wrote:
> > 
> > > Hi all,  
> > > I've got a 5 node elasticsearch cluster that has 3 machines with a  
> > > "node.storage: ssd\_fast" and 2 with "node.storage: sata\_slow" attributes.  
> > > I'd like to write today's index (this is being used for logstash) to the  
> > > ssd machines, and then use the slow ones for archiving shards.
> > > 
> > > Here's the error I"m getting when I try to change the index routing (for  
> > > all existing indexes):
> > > 
> > > curl -XPUT es3:9200/\_settings -d '{  
> > > "index" : {  
> > > "index.routing.allocation.include.node.storage" : "ssd\_fast"  
> > > }  
> > > }'
> > > 
> > > {"error":"RemoteTransportException[[es3][inet[/10.123.123.103:9300]][indices/settings/update]];  
> > > nested: ElasticsearchIllegalArgumentException[Can't update non dynamic  
> > > settings[[index.index.routing.allocation.include.node.storage]] for  
> > > open indices[[logstash-sfo1-2014.04.09, logstash-sfo1-2014.04.08,  
> > > kibana-int]]]; ","status":400}k
> > > 
> > > Any pointers appreciated, thanks.
> > > 
> > > -Ryan
> > > 
> > > --  
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%  
> > > [40googlegroups.com](http://40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > 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).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Yr\_jh84-poiMqFEiVC0uzX\_ausDmXW7DPuBnhmXkfdqA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Yr_jh84-poiMqFEiVC0uzX_ausDmXW7DPuBnhmXkfdqA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ryan\_Bellows](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Ryan\_Bellows](https://discuss.elastic.co/u/Ryan_Bellows)\
**Post date:** [April 9, 2014, 7:17pm UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/5 "2014-04-09T19:17:54Z")

</div>

The nodes all have that value in their elasticsearch.yml files, and have  
been restarted since then.

I'm getting the error trying to update indexes to store their shards only  
on those nodes with the appropriate node.storage value. I was under the  
impression that was a basic way to do shard routing, am I mistaken?

-R

On Tuesday, April 8, 2014 6:01:24 PM UTC-7, Mark Walkom wrote:

> Ok, but you can't dynamically update them, you can only ever define them  
> in the .yml and then restart the service for the value to be changed.
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \<javascript:\>  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 9 April 2014 10:59, Ryan Bellows \<[r...@weebly.com](mailto:r...@weebly.com) \<javascript:\>\> wrote:
> 
> > Ah, to be clear, those attributes are already in the elasticsearch.yml  
> > files on all 5 servers.
> > 
> > On Tuesday, April 8, 2014 5:53:43 PM UTC-7, Mark Walkom wrote:
> > 
> > > You need to put that into the elasticsearch.yml and then restart each  
> > > node.
> > > 
> > > Regards,  
> > > Mark Walkom
> > > 
> > > Infrastructure Engineer  
> > > Campaign Monitor  
> > > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com)  
> > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> > > 
> > > On 9 April 2014 10:46, Ryan Bellows [r...@weebly.com](mailto:r...@weebly.com) wrote:
> > > 
> > > > Hi all,  
> > > > I've got a 5 node elasticsearch cluster that has 3 machines with a  
> > > > "node.storage: ssd\_fast" and 2 with "node.storage: sata\_slow" attributes.  
> > > > I'd like to write today's index (this is being used for logstash) to the  
> > > > ssd machines, and then use the slow ones for archiving shards.
> > > > 
> > > > Here's the error I"m getting when I try to change the index routing  
> > > > (for all existing indexes):
> > > > 
> > > > curl -XPUT es3:9200/\_settings -d '{  
> > > > "index" : {  
> > > > "index.routing.allocation.include.node.storage" : "ssd\_fast"  
> > > > }  
> > > > }'
> > > > 
> > > > {"error":"RemoteTransportException[[es3][inet[/10.123.123.103:9300]][indices/settings/update]];  
> > > > nested: ElasticsearchIllegalArgumentException[Can't update non dynamic  
> > > > settings[[index.index.routing.allocation.include.node.storage]] for  
> > > > open indices[[logstash-sfo1-2014.04.09, logstash-sfo1-2014.04.08,  
> > > > kibana-int]]]; ","status":400}k
> > > > 
> > > > Any pointers appreciated, thanks.
> > > > 
> > > > -Ryan
> > > > 
> > > > --  
> > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%  
> > > > [40googlegroups.com](http://40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3d3d6edd-6b57-4c0c-8e6d-dd98f8aa84dc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > > .  
> > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > > 
> > > --  
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ca9f34ae-5fa1-4771-b4e7-daf272c1c024%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/a56036fa-71ce-4dca-ad6b-33027f834d84%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a56036fa-71ce-4dca-ad6b-33027f834d84%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![oleg-andreyev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleg-andreyev/32/8799_2.png) [@oleg-andreyev](https://discuss.elastic.co/u/oleg-andreyev)\
**Post date:** [October 24, 2016, 1:25pm UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/6 "2016-10-24T13:25:53Z")

</div>

I'm definitely late, but your query is wrong. Today I've faced exact the same issue.  
It should be:

```auto
curl -XPUT "http://localhost:9200/test/_settings" -d'
{
  "index.routing.allocation.include.indexing": false
}'

```

or

```auto
curl -XPUT "http://dev-es2.i.intexsys.lv:9200/opcart_opticsplanet_test_2016-10-24-155301/_settings" -d'
{
  "index": {
    "routing.allocation.include.indexing": false
  }
}'

```

but not

```auto
curl -XPUT "http://dev-es2.i.intexsys.lv:9200/opcart_opticsplanet_test_2016-10-24-155301/_settings" -d'
{
  "index": {
    "index.routing.allocation.include.indexing": false
  }
}'

```

---

<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:** [July 5, 2017, 10:10pm UTC](https://discuss.elastic.co/t/setting-index-routing-allocation-include-node-failure/16881/7 "2017-07-05T22:10:14Z")

</div>