❦ 22 février 2014 14:55 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as they don't go to the same destination ip:ports
since a connection is
Hi Vincent,
On Sun, Feb 23, 2014 at 10:25:18AM +0100, Vincent Bernat wrote:
??? 22 février 2014 14:55 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port
Hello
Regarding restarts, rather that cold starts, if you configure peers the
state from before the restart should be kept. The new process haproxy
creates is automatically a peer to the existing process and gets the state
as was.
Neil
On 23 Feb 2014 03:46, Patrick Hemmer hapr...@stormcloud9.net
❦ 23 février 2014 10:31 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as they don't go to the same destination ip:ports
since a connection is
On Sun, Feb 23, 2014 at 12:09:11PM +0100, Vincent Bernat wrote:
??? 23 février 2014 10:31 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as
❦ 23 février 2014 12:25 CET, Willy Tarreau w...@1wt.eu :
I suppose this is in combination with SO_REUSEADDR (otherwise, bind()
would fail). It's good to know:
tcpESTAB 0 0 192.168.116.1:3754474.125.132.104:80
tcpESTAB 0 0
Neil,
Yes, peers are great for passing stick tables to the new HAProxy
instance and any current connections bound to the old process will be
fine.
However any new connections will hit the new HAProxy process and if
the backend server is down but haproxy hasn't health checked it yet
then the user
7 matches
Mail list logo
