I think you are observing a master change when you restart a master node,
for example when installing plugins. That is expected. Because the node you
restart is going down, it disconnects from the cluster, and the discovery
module must elect a new master. But, since all nodes are equal, and each
one can become the master node, it will not have much effects. AFAIK the
master node is only responsible for broadcasting a new cluster state to all
other nodes. The master node in Elasticsearch is not comparable to the
master in the commonly known master/slave communication model. So you
shouldn't worry too much about master node changes.
On Thursday, July 19, 2012 5:17:46 PM UTC+2, Tim J wrote:
Is there any way to force the election of a new master? I've run into a
few situations where I need to make changes to all nodes in my cluster,
either to update a plugin or to update configuration and it's always
problematic when I get to the master. It would be nice if I could force a
new master to be elected in an orderly manner so that it doesn't just get
pulled out from under the cluster. Does such an option exist?