Expected behaviour of routing enable


(Mohit Anchlia) #1

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.
To view this discussion on the web visit 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.


(Binh Ly-2) #2

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8a32664f-dcb1-4214-ab27-113c086fe044%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #3