Q: Is using the automatic node naming where every time I bounce a node I
get a new node name interfering with restarting from the local gateway?
Q Background:
So previously, I asked about bouncing nodes, because it seems that
whenever I bounce a node, it has to regenerate the node from the
Unless I misread the post, your scenario seems to be the normal behavior.
If you restart a node with allocation disabled, it will have no shards.
Re-enabling allocation will force the shards on the node to be active. This
behavior is at least what I have experienced. Perhaps there should be a
Reading the description of that issue, I don't think they're the same.
Looking at the code... Yeah, that's only about moving primaries around.
So is there a way to restart a node without it going to zero shards and
then back again?
--
You received this message because you are subscribed to
I do not think there is a way, but perhaps someone else can correct me. One
potential way is to instead of disabling allocation, to set a timeout value
high enough that the node can fully restart before the cluster drops the
node. However, I am not sure if a node that is being cleanly shutdown
