# Expected behaviour of routing enable

**URL:** <https://discuss.elastic.co/t/expected-behaviour-of-routing-enable/16798>\
**Category:** Elasticsearch\
**Created:** [April 3, 2014, 5:29pm UTC](https://discuss.elastic.co/t/expected-behaviour-of-routing-enable/16798 "2014-04-03T17:29:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\
**Post date:** [April 3, 2014, 5:29pm UTC](https://discuss.elastic.co/t/expected-behaviour-of-routing-enable/16798/1 "2014-04-03T17:29:59Z")

</div>

I was doing a quick restart so I ran the following command  
{"transient":{"cluster.routing.allocation.enable":"none"}} and disabled  
allocation. I stopped one of the nodes and in the "head" UI all the shards  
went to UNASSIGNED. I then brought the node back up, at this point I was  
expecting it to move these shards back to the node, but it didn't move  
them. I had to run  
{"transient":{"cluster.routing.allocation.enable":"all"}}. Is this expected  
even for "transient" mode?

--  
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/CAOT3TWqmDiG6nzfuVgJjJtsVmVV-Z41Wor\_RVE-RobrhzjVk%3DA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWqmDiG6nzfuVgJjJtsVmVV-Z41Wor_RVE-RobrhzjVk%3DA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Binh\_Ly\_2](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@Binh\_Ly\_2](https://discuss.elastic.co/u/Binh_Ly_2)\
**Post date:** [April 3, 2014, 9:55pm UTC](https://discuss.elastic.co/t/expected-behaviour-of-routing-enable/16798/2 "2014-04-03T21:55:59Z")

</div>

The transient setting was still in effect because your cluster was still up  
(even though 1 node was down). If instead your entire cluster went down,  
then when you bring it back up, the transient setting is no longer in  
effect.

--  
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/8a32664f-dcb1-4214-ab27-113c086fe044%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8a32664f-dcb1-4214-ab27-113c086fe044%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 1:38am UTC](https://discuss.elastic.co/t/expected-behaviour-of-routing-enable/16798/3 "2017-07-06T01:38:20Z")

</div>


