# Failover ElasticSearch .Net Client **URL:** \ **Category:** Elasticsearch\ **Created:** [May 15, 2012, 10:57pm UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710 "2012-05-15T22:57:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Vinicius\_Melo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_melo/32/2720_2.png) [@Vinicius\_Melo](https://discuss.elastic.co/u/Vinicius_Melo)\ **Post date:** [May 15, 2012, 10:57pm UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710/1 "2012-05-15T22:57:49Z")
I have the following situation: I have a .NET client in clustered Windows Servers in AWS. I want to deal with failover, but since my client runs in Windows the solution of starting a ES node in the same server doesn't apply. What's the best solution in this scenario? I want to understand and know how to deal with the security issue related to Elastic Load Balancer mentioned by _rbrc_, because one solution would be to use ELB. If possible, I would like to understand more about the following items and how one or some of them could help me: - No-data server and EC2 discovery; - Nginx authentication with the ELB solution; - Using HAProxy instead of ELB. ---
**Author:** ![medcl\_net](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@medcl\_net](https://discuss.elastic.co/u/medcl_net)\ **Post date:** [May 16, 2012, 2:20am UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710/2 "2012-05-16T02:20:25Z")
hi,if you are using my [ElasticSearch.NET](http://ElasticSearch.NET)(i guess),you already have this feature,the fallover is done inside the [ElasticSearch.NET](http://ElasticSearch.NET),there is a connection pool config like this: you can specify more than one node within the cluster,the client will auto-detect the failure connection,and then disable it,is that what you want? From: Vinicius Melo Sent: Wednesday, May 16, 2012 6:57 AM To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) Subject: Failover ElasticSearch .Net Client I have the following situation: I have a .NET client in clustered Windows Servers in AWS. I want to deal with failover, but since my client runs in Windows the solution of starting a ES node in the same server doesn't apply. What's the best solution in this scenario? I want to understand and know how to deal with the security issue related to Elastic Load Balancer mentioned by rbrc, because one solution would be to use ELB. If possible, I would like to understand more about the following items and how one or some of them could help me: - No-data server and EC2 discovery; - Nginx authentication with the ELB solution; - Using HAProxy instead of ELB. ---
**Author:** ![Vinicius\_Melo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_melo/32/2720_2.png) [@Vinicius\_Melo](https://discuss.elastic.co/u/Vinicius_Melo)\ **Post date:** [May 16, 2012, 6:03pm UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710/3 "2012-05-16T18:03:11Z")
Hello, I'm would like to have something that i would point node ip's and it would automatically discover which one is the master to send correctly the requests, as i'm using EC2 Discovery it would be possible but i didn't discovered how to do it using Nest as i'm using it. Does anybody now how could i deal with it? Is it possible just implementing a HA Proxy Load balancer, or can i do it in another way, maybe using the Cluster Api. Thanks Em terça-feira, 15 de maio de 2012 23h20min25s UTC-3, Medcl escreveu: > hi,if you are using my [ElasticSearch.NET](http://ElasticSearch.NET)(i guess),you already have this > feature,the fallover is done inside the [ElasticSearch.NET](http://ElasticSearch.NET),there is a > connection pool config like this: > > > > > > > you can specify more than one node within the cluster,the client will > auto-detect the failure connection,and then disable it,is that what you > want? > > _From:_ Vinicius Melo [viniciusfbm@gmail.com](mailto:viniciusfbm@gmail.com) > _Sent:_ Wednesday, May 16, 2012 6:57 AM > _To:_ [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > _Subject:_ Failover Elasticsearch .Net Client > > I have the following situation: I have a .NET client in clustered Windows > Servers in AWS. I want to deal with failover, but since my client runs in > Windows the solution of starting a ES node in the same server doesn't > apply. What's the best solution in this scenario? > > I want to understand and know how to deal with the security issue related > to Elastic Load Balancer mentioned by _rbrc_, because one solution would > be to use ELB. If possible, I would like to understand more about the > following items and how one or some of them could help me: > > - No-data server and EC2 discovery; > - Nginx authentication with the ELB solution; > - Using HAProxy instead of ELB. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 17, 2012, 10:15pm UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710/4 "2012-05-17T22:15:00Z")
Why can't you start a local client node on windows? On Wed, May 16, 2012 at 9:03 PM, Vinicius Melo [viniciusfbm@gmail.com](mailto:viniciusfbm@gmail.com)wrote: > Hello, > > I'm would like to have something that i would point node ip's and it would > automatically discover which one is the master to send correctly the > requests, as i'm using EC2 Discovery it would be possible but i didn't > discovered how to do it using Nest as i'm using it. Does anybody now how > could i deal with it? > > Is it possible just implementing a HA Proxy Load balancer, or can i do it > in another way, maybe using the Cluster Api. > > Thanks > > Em terça-feira, 15 de maio de 2012 23h20min25s UTC-3, Medcl escreveu: > > > hi,if you are using my [ElasticSearch.NET](http://ElasticSearch.NET)(i guess),you already have > > this feature,the fallover is done inside the [ElasticSearch.NET](http://ElasticSearch.NET),there is a > > connection pool config like this: > > > > > > > > > > > > > > you can specify more than one node within the cluster,the client will > > auto-detect the failure connection,and then disable it,is that what you > > want? > > > > _From:_ Vinicius Melo [viniciusfbm@gmail.com](mailto:viniciusfbm@gmail.com) > > _Sent:_ Wednesday, May 16, 2012 6:57 AM > > _To:_ [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > > _Subject:_ Failover Elasticsearch .Net Client > > > > I have the following situation: I have a .NET client in clustered Windows > > Servers in AWS. I want to deal with failover, but since my client runs in > > Windows the solution of starting a ES node in the same server doesn't > > apply. What's the best solution in this scenario? > > > > I want to understand and know how to deal with the security issue related > > to Elastic Load Balancer mentioned by _rbrc_, because one solution would > > be to use ELB. If possible, I would like to understand more about the > > following items and how one or some of them could help me: > > > > - No-data server and EC2 discovery; > > - Nginx authentication with the ELB solution; > > - Using HAProxy instead of ELB. ---
**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:28am UTC](https://discuss.elastic.co/t/failover-elasticsearch-net-client/7710/5 "2017-07-06T03:28:18Z")