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.
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
From: Vinicius Melo firstname.lastname@example.org
Sent: Wednesday, May 16, 2012 6:57 AM
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.