# Bug when failing over using rancher and Nest

**URL:** <https://discuss.elastic.co/t/bug-when-failing-over-using-rancher-and-nest/81343>\
**Category:** Elasticsearch\
**Created:** [April 5, 2017, 4:41pm UTC](https://discuss.elastic.co/t/bug-when-failing-over-using-rancher-and-nest/81343 "2017-04-05T16:41:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![imranazad](https://avatars.discourse-cdn.com/v4/letter/i/c2a13f/32.png) [@imranazad](https://discuss.elastic.co/u/imranazad)\
**Post date:** [April 5, 2017, 4:41pm UTC](https://discuss.elastic.co/t/bug-when-failing-over-using-rancher-and-nest/81343/1 "2017-04-05T16:41:17Z")

</div>

I am using a docker container that is a search api making use of Nest 2.0.2, the container talks to another container which is a load balancer for two elastic search instances. What I've noticed is that when one of the the elastic search instances goes down, the search API is unable to call elastic via the load balancer, despite the fact that I can curl on the box to the load balancer which returns a response from the single elastic instance that is still up. The elasticsearch instances are not a cluster they are just separate instances.

Any ideas what's going on?

---

<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:** [May 3, 2017, 4:41pm UTC](https://discuss.elastic.co/t/bug-when-failing-over-using-rancher-and-nest/81343/2 "2017-05-03T16:41:31Z")

</div>

Closed on May 3, 2017, 4:41pm UTC

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