Question on ES cluster when MasterNode die

Hi pros,

Suppose I have a ES cluster with 2 nodes : [Node1 / 192.168.100.1] ---
[Node2 / 192.168.100.2]

And a client running Kibana point to the Node1 IP : 192.168.100.1

According to elastic config file : /etc/elasticsearch/elasticsearch.yml

ElasticSearch takes care about load balancing, relocating, gathering the

results from nodes, etc. Experiment with different settings to fine-tune

your setup.

Suppose that the Node1 is died ! that's mean the IP 192.168.100.1 is also
dead too.

The question is : will the Node2 take over the IP 192.168.100.1 ? or I've
to manually config the client-kibana to point to the Node2 IP to keep
running ?

Hope someone will guide me this.

Thanks alot.

Atrus@.

--
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.

Hi Artus,

The comment means that for every request Elasticsearch get, it will load
balance the effort using all the available nodes in the cluster. However,
it only can do that after a TCP connection has been made to one of the
ports it listen on. If your Node1 dies, so does the ES process on it and no
one will listen on that port. Most people solve this by load balancing
their incoming Kibana requests to multiple nodes, using for example
nginx: http://wiki.nginx.org/LoadBalanceExample

Cheers,
Boaz

On Thursday, July 18, 2013 10:01:23 AM UTC+2, Atrus Klaus wrote:

Hi pros,

Suppose I have a ES cluster with 2 nodes : [Node1 / 192.168.100.1] ---
[Node2 / 192.168.100.2]

And a client running Kibana point to the Node1 IP : 192.168.100.1

According to elastic config file : /etc/elasticsearch/elasticsearch.yml

ElasticSearch takes care about load balancing, relocating, gathering the

results from nodes, etc. Experiment with different settings to fine-tune

your setup.

Suppose that the Node1 is died ! that's mean the IP 192.168.100.1 is also
dead too.

The question is : will the Node2 take over the IP 192.168.100.1 ? or
I've to manually config the client-kibana to point to the Node2 IP to keep
running ?

Hope someone will guide me this.

Thanks alot.

Atrus@.

--
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.