You can handle that with a load balancer, in your app, or use DNS round
robin or something similar.
There's nothing native to ES that'll handle it.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com
On 28 October 2013 19:43, dan dan.tuffery@gmail.com wrote:
If I have 5 ES nodes in my cluster which ES node should should my clients
point to, the master node? If the master node goes down and a new one is
elected how will my client communicate with Elasticsearch, they will still
be pointing the the node that is down?On Sunday, October 27, 2013 1:56:31 PM UTC, Jörg Prante wrote:
If you will access with two clients only, there is almost no need in
preparing extra nodes for them.Criteria for setting up HTTP proxy nodes are massive parallel HTTP
accesses (a few hundred requests in parallel) and large result sets, which
can legitimate a separation of index/search data nodes from proxy nodes for
HTTP traffic handling and response generation phase.Jörg
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.