I have 8 data nodes and 6 coordinator nodes in an active cluster running
I want to upgrade to 1.3.1
the upgrade docs am I correct to assume:
a) disable shard allocation before doing anything
b) proceed to upgrade each node to 1.3.1
c) only after ALL nodes are @ 1.3.1 then I can re-enable shard allocation.
My question is that at some point during the upgrade of all the data nodes,
the shards on them will be "unassigned" and the cluster will not
So in other words running some nodes as 1.2.1 and others as 1.3.1 with
shard allocation enabled is NOT advised and in general cluster
un-availability is expected due to shards being in an unassigned state as
each data node is upgraded.
At least this is the behavior I see today, (not during an upgrade) when I
disable allocation and restart a node, those shards are unassigned until I
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a7c8a15b-3e74-4c38-ab03-ff3e7d6fcd32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.