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?
So previously, I asked about bouncing nodes, because it seems that
whenever I bounce a node, it has to regenerate the node from the other
nodes in the cluster.
Someone told me I needed to lock shard allocation, then bounce, because
the problem was that the cluster was reallocating the shards off of the
node, so then the node wouldn't just
come back up from the local gateway.
I've tried that, and it doesn't seem to work. What happens is when the
instance shutdown, all of its shards go into "unallocated". Then when I
startup the instance, the node comes up with zero shards until I unlock
shard allocation. So the locking didn't seem to help.
I'm wondering if the problem is because all of my nodes are named
automatically using the marvel characters list, so essentially the node
name changes each time. So the lock/unlock doesn't help, because the
cluster is expecting a node with a specific name and when it doesn't find
it, it initializes the node with no shards.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5a6401b1-d6a9-4aad-807f-01f4c47a63d7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.