# Load balancer(HAproxy) causing data lost

**URL:** <https://discuss.elastic.co/t/load-balancer-haproxy-causing-data-lost/39481>\
**Category:** Elasticsearch\
**Created:** [January 18, 2016, 8:46pm UTC](https://discuss.elastic.co/t/load-balancer-haproxy-causing-data-lost/39481 "2016-01-18T20:46:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaizh89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaizh89/32/7225_2.png) [@kaizh89](https://discuss.elastic.co/u/kaizh89)\
**Post date:** [January 18, 2016, 8:46pm UTC](https://discuss.elastic.co/t/load-balancer-haproxy-causing-data-lost/39481/1 "2016-01-18T20:46:52Z")

</div>

Hi guys,

I have been running a small, 3-node, ES 1.4.5 cluster. I put a load balancer(HAproxy 1.4.24) in front of it to balance write requests from an Apache Storm topology.  
I realised I was loosing some data, and having a look at the Storm logs I could see instances of this error:

2016-01-01T13:02:56.467+0000 STDIO [INFO] ERROR: None of the configured nodes were available: [[ES1][SzFmCc3-T16H0Q7Z9En9Nw][es1][inet[/10.0.0.28:9300]]]

10.0.0.28 is the IP of the load balancer.

I tried removing the load balancer and just add all the node addresses to a java TransportClient. So far, removing the LB layer seems to have fixed the issue.

Does any one have any clue on why this was happening? I'm trying to figure out if this is really a good solution for the issue.

Thanks.

---

<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 5, 2017, 11:23pm UTC](https://discuss.elastic.co/t/load-balancer-haproxy-causing-data-lost/39481/2 "2017-07-05T23:23:38Z")

</div>