# Elasticsearch &"Load Balance One Cluster Node"

**URL:** <https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220>\
**Category:** Elasticsearch\
**Created:** [March 2, 2018, 9:54am UTC](https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220 "2018-03-02T09:54:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ben96](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben96/32/28334_2.png) [@Ben96](https://discuss.elastic.co/u/Ben96)\
**Post date:** [March 2, 2018, 9:54am UTC](https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220/1 "2018-03-02T09:54:52Z")

</div>

Hello everyone, hope you are all fine 🙂

Few questions today !

Context :

Someone in my compagny is using Shiny (R) on our Stack ELK Clusters, the thing is, that he need one of our 3 frontend machines to be at 100% SLA (Alive all time if you prefer), else it's application "plugged" into the cluster will be down. And we MUST prevent this.

So my question is : is it possible, by any "way" to setup a solution that make this SPECIFIC machine (like machineA) load balanced (?) by machineB and machineC in case she's down ?

We already have set a Load Balancer (F5) for these three frontend ( They run kibana in addition to Elastic CLIENT)

It may not be very clear, I agree  
I would appreciate any feedback and advice

Cordially, Ben.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 2, 2018, 3:49pm UTC](https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220/2 "2018-03-02T15:49:30Z")

</div>

It's normally something you try to solve on the client side by giving it 3 nodes to talk to.

All our clients support that.

If you have a load balancer in front of the Elasticsearch REST endpoint (9200), then you can also use it.

---

<div class="post-metadata">

**Author:** ![Ben96](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben96/32/28334_2.png) [@Ben96](https://discuss.elastic.co/u/Ben96)\
**Post date:** [March 3, 2018, 7:56pm UTC](https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220/3 "2018-03-03T19:56:55Z")

</div>

Hi David,

All nodes are currently configured for `Load Balacing & HA`with Elastic params (discover etc..)

We found the solution of our Issue, as you mentioned in your reply, we will do some Load Balacing on the 9200 Port.

With that, we will add a DNS entry name, like : `client-elk.domain.tld` and add all nodes needed with 9200 Port.

Then, all applications needed to be "plugged" on the Cluster will use the `client-elk.domain.tld:9200` and it will be "always" available as we need.

Thanks you for you reply and good advice.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 31, 2018, 7:56pm UTC](https://discuss.elastic.co/t/elasticsearch-load-balance-one-cluster-node/122220/4 "2018-03-31T19:56:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.