Thank you both Elvar and Jorg for your replies.
Aaron
On Thursday, December 4, 2014 7:58:07 AM UTC-5, Elvar Böðvarsson wrote:
>
> Two options
>
> 1. Have a client instance of elasticsearch on a different server or on the
> same server that does the query. That node must be set to master=false
With Java client, you have not to worry about that. You have either
multiple node connections or explicitly chosen the nodes to connect to
(transport client).
With HTTP client, the official Elasticsearch clients provide methods to
connect to multiple hosts. If one host goes down, the next one is c
Two options
1. Have a client instance of elasticsearch on a different server or on the
same server that does the query. That node must be set to master=false and
data=false. Being a member of the cluster means you know where the data is.
2. Use a http reverse proxy that connects to all the nodes
This is a newbie question about how the cluster works. I try to find the
answer from the group, but seems not exact the same question I have.
By reading the guide from elasticsearch.com, I understand when a master
node goes down, a new master node will be elected automatically. However, a
client
