Failover ElasticSearch .Net Client


(Vinicius Melo) #1

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.

(medcl.net) #2

hi,if you are using my ElasticSearch.NET(i guess),you already have this feature,the fallover is done inside the 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
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.

(Vinicius Melo) #3

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(i guess),you already have this
feature,the fallover is done inside the 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
Sent: Wednesday, May 16, 2012 6:57 AM
To: 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.

(Shay Banon) #4

Why can't you start a local client node on windows?

On Wed, May 16, 2012 at 9:03 PM, Vinicius Melo viniciusfbm@gmail.comwrote:

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(i guess),you already have
this feature,the fallover is done inside the 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
Sent: Wednesday, May 16, 2012 6:57 AM
To: 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.

(system) #5