The elected master node is not related to where queries are routed. Same for elected primary shards. Searches are round robin between shard copies. You can control it by using shard allocation awareness (which will come handy when you have more nodes in the cluster to make sure copies of the shards are allocated properly across the two zones) which will also make sure that requests will go first to shards in their own zone. More info here: Elasticsearch Platform — Find real-time answers at scale | Elastic.
On Saturday, January 28, 2012 at 2:43 AM, Shane Witbeck wrote:
I have 2 boxes in a cluster that are geographically diverse (one on east coast and one on west coast). The behavior I observe is that it does a round robin (I'm making an assumption here based on every other response time being much slower). Is there a way to configure the cluster so all queries go to the master and only get routed to the non-master (further away, less performant) if there's a failure on the master?