So if I understand Zen unicast discovery right, we have elasticsearch
running on a set of nodes with fixed IPs (gossip routers). Any new node
talks to these nodes first to "register" itself as part of the cluster.
Client nodes can obtain the master node (or data nodes) from the cluster by
talking to one of these routers. Needless to say at least one of the gossip
routers must be up at all times, otherwise discovery fails. Can we
dynamically add more gossip routers or would that require us to shutdown the
node, update its config file and restart it?
On Tue, Aug 16, 2011 at 4:09 AM, kimchy [via ElasticSearch Users] <
On Sat, Aug 13, 2011 at 11:02 PM, optimusprime <[hidden email]http://user/SendEmail.jtp?type=node&node=3258336&i=0
I'm not entirely sure how discovery in ES works. Are there resources out
there that detail it? How can I dynamically add a new node (on a different
physical machine) to an existing cluster. I tried looking at some previous
posts in this forum. I get the idea that one's supposed to list nodes in
config file and they discover each other. But that doesn't quite explain
dynamic addition of nodes and load balancing.
Discovery is explained here:
On the same lines, is the master elected or configured? Does the master
more resources than data nodes? Because in the latter case, I would like
have a machine with more physical resources be the master.
Master is automatically elected, but it does not require more resources.
You can control which nodes will can become master nodes though.
View this message in context:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
If you reply to this email, your message will be added to the discussion
To unsubscribe from Adding new nodes, click herehttp://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3252115&code=dXNtYXNvb2RAZ21haWwuY29tfDMyNTIxMTV8LTE2MzM1MTU2MDg=.