# Question on ES cluster when MasterNode die **URL:** \ **Category:** Elasticsearch\ **Created:** [July 18, 2013, 8:01am UTC](https://discuss.elastic.co/t/question-on-es-cluster-when-masternode-die/12836 "2013-07-18T08:01:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Atrus\_Klaus](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Atrus\_Klaus](https://discuss.elastic.co/u/Atrus_Klaus)\ **Post date:** [July 18, 2013, 8:01am UTC](https://discuss.elastic.co/t/question-on-es-cluster-when-masternode-die/12836/1 "2013-07-18T08:01:23Z")
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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [July 18, 2013, 10:03am UTC](https://discuss.elastic.co/t/question-on-es-cluster-when-masternode-die/12836/2 "2013-07-18T10:03:39Z")
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: [Simple Load Balancing | 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:25am UTC](https://discuss.elastic.co/t/question-on-es-cluster-when-masternode-die/12836/3 "2017-07-06T02:25:47Z")