actually there is a master node. You can read what Shay explained about
master node at sematext blog interview here (check comments section too):
A master in elasticsearch is responsible for handling nodes coming and going
and allocation of shards. Note, the master is not a single point of failure,
if it fails, then another node will be elected as master. Also note, that
nodes do not need to communicate with the master on each request, so its not
a single point of bottleneck.
As for the massive deployment (thousands of nodes) I do not have experience
but I think there are other factors that can slow down performance
significantly depending on cluster setup as sharding and replication needs
to take place (though they can run on background the communication inside
the cluster needs to happen between nodes and I think it would be much more
data intensive communication compared to node-master communication). As for
the cluster setup and other critical info AFAIK it should be persisted via
gateway so if anything goes wrong and the cluster crashes there should be
way how to recover.
On Fri, May 28, 2010 at 10:41 PM, Berkay Mollamustafaoglu <firstname.lastname@example.org
Why do you say there is a master? AFAIK, all nodes are equal.
mberkay on yahoo, google and skype
On Fri, May 28, 2010 at 2:40 AM, ray.qi email@example.com wrote:
There is only one single master in the cluster (automatically elected),
since the master node maintains some critical information, I doubt if it
will be the bottleneck when we have thousands of nodes. For master-node
communication, is Zookeeper a better choice?
View this message in context:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.