# Http loadbalancers vs smart elasticsearch loadblalncers

**URL:** <https://discuss.elastic.co/t/http-loadbalancers-vs-smart-elasticsearch-loadblalncers/6153>\
**Category:** Elasticsearch\
**Created:** [December 13, 2011, 11:18pm UTC](https://discuss.elastic.co/t/http-loadbalancers-vs-smart-elasticsearch-loadblalncers/6153 "2011-12-13T23:18:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Piavlo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/piavlo/32/1214_2.png) [@Piavlo](https://discuss.elastic.co/u/Piavlo)\
**Post date:** [December 13, 2011, 11:18pm UTC](https://discuss.elastic.co/t/http-loadbalancers-vs-smart-elasticsearch-loadblalncers/6153/1 "2011-12-13T23:18:33Z")

</div>

Hi,

There is elasticsearch cluster and app running on elastic size webfarm  
which need to access the elasticsearch cluster.

Initially I was thinking to run haproxy locally on each webserver in the  
farm.  
But running elasticsearch with no data as smart loadbalancer is very  
attractive.  
So I want to under stand if it's a good idea to run it in the following  
setup.

I want to run elasticsearch with node.data set to false on each  
webserver node.  
From documentation it is not clear which role these nodata  
elasticsearch nodes play in Gateway module recovery.

Say there is a cluster of 3 nodes with replication=1 and

gateway:  
type: local  
recover\_after\_nodes: 2  
recover\_after\_time: 1m  
expected\_nodes: 3

Since the nodata elasticsearch nodes is dynamic and it's also not clear  
if such nodes have effect on the recovery, is the above gateway  
configuration stays the same or should be changed?

Any other issues I need to consider?

Thanks  
Alex  
||||

---

<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:** [July 6, 2017, 3:45am UTC](https://discuss.elastic.co/t/http-loadbalancers-vs-smart-elasticsearch-loadblalncers/6153/2 "2017-07-06T03:45:26Z")

</div>

Closed on July 6, 2017, 3:45am UTC


