On 21 January 2014 13:17, Vinoth M vinoth@ericsson.com wrote:
Hi,
1) I am using Solaris 10 x86.Could you please let me know if there a pre
compiled package available for it.
2) Also let me know if HAproxy is supported for Solaris 10 x86.
I can't help with these 2 questions ...
Thanks for the reply. I am running 1.5-dev21-6b07bf7.
I wrote a script to perform netstat dump every second and track how long my
connections are. If tunnel timeout is set to 3600s, the connects are like
these:
192.168.78.155:43089 disappeared at 1390317336, lasted 3600
192.168.78.155:43090
Is there a way to limit the number of sticky connections to a single server?
I would like to have all traffic to a given virtual host tend to end up on
the same backend server, but also allow the traffic to spread to multiple
servers if more than say 50 connections are already stuck to a given
Hi Michael,
Seems like you keep wanting to use the hdr(host), can i ask why?
You seem to explain you just want to stick 'src' to a 'server'.. So why
configure hdr(host) ?
Can you try this config? (ps 60 seconds isnt verry long..)
listen http
balance roundrobin
stick-table type ip size
You are correct, 60 seconds is not long. Just long enough to exceed my NFS
caching on the backend.
The reason for wanting to use hdr(host) is because this will make better
use of the resources in my cluster (I have thousands of domains/web
applications on this cluster).
The reason I was
*From: *Malcolm Turnbull malc...@loadbalancer.org
*Sent: * 2014-01-14 07:13:27 E
*To: *haproxy@formilux.org haproxy@formilux.org
*Subject: *Just a simple thought on health checks after a soft reload of
HAProxy
Just a simple though on health checks after a soft reload of HAProxy
If for
Hi,
On Sat, Jan 18, 2014 at 11:25:56AM +0800, Ge Jin wrote:
Hi, all!
I was confused when we use haproxy and option http-kee-alive, the
established is as twice as tunnel. But other tcp status stayed the
same level.
#the tunnel mode
LISTEN 5
FIN_WAIT_1 325
FIN_WAIT_2 254
SYN_SENT 49
7 matches
Mail list logo