On Fri, Mar 28, 2014 at 09:29:23AM +0100, basti wrote:
> SRV1 -> Node 1
> client -->|(shared IP) \/
> | /\
> SRV2 -> Node 2
> :
> Node n
>
> Can
Denis thanks for your "nutshell explanation"
I will try the following:
SRV1 -> Node 1
client -->|(shared IP) \/
| /\
SRV2 -> Node 2
:
Node n
SRV
Le 27/03/2014 18:21, Denis Witt a écrit :
On Thu, 27 Mar 2014 16:47:15 +0100
basti wrote:
perhaps that's a bit off topic here but can someone explain what I
need to build a hardware failover nginx cluster?
I a nutshell:
* (at least) two Servers
* a monitoring software
* a shared IP
On Thu, 27 Mar 2014 16:47:15 +0100
basti wrote:
> perhaps that's a bit off topic here but can someone explain what I
> need to build a hardware failover nginx cluster?
I a nutshell:
* (at least) two Servers
* a monitoring software
* a shared IP
* something that will switch the shared IP
On Thu, Mar 27, 2014 at 04:47:15PM +0100, basti wrote:
> Hello,
> perhaps that's a bit off topic here but can someone explain what I need
> to build a hardware failover nginx cluster?
>
> The unclear is:
> How does the client know that the server 1 is down and use the other one?
> DNS failover has
Hi,
> perhaps that's a bit off topic here but can someone explain what I need to
> build a hardware failover nginx cluster?
Nope, but define hardware. A loadbalancer does not care what OS you are
running, it does care what service it needs to balance. So, would "a debian
server running loadbala
6 matches
Mail list logo