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.
Em quinta-feira, 9 de fevereiro de 2012 16h08min35s UTC-2, rbrc escreveu:
I'm setting up elasticsearch in AWS and I'm trying to figure out how
to deal with a node going down. Specifically, if I have 2 ES servers
[s01, s02], and my app is configured to always hit s01, how can i get
it to failover to s02 if s01 goes down? My first thought was to put
ES behind an ELB which has health monitoring built in, but there is no
way to do a private internal only ELB so if I did this then ES would
be public to the world, which is clearly a bad idea. We are using
nodejs and I haven't yet found a library for it to do this failover
for me. I could write one I suppose but I'd rather avoid that if
possible.