Very true...
There are some nice examples in the docs.
You could also use the persist option to keep old users on the server
while new ones go to other servers.
I use that to make sure i dont kick users..
regards.
On Aug 19, 2009, at 7:59 PM, Bernhard Krieger wrote:
Hi,
i use the option "httpcheck" on the backend servers.
If i remove the file, the backend seems to be down and no external
requests are forwarded...
But you can still maintain your backend server using its real ip.
I created an alias too (DISABLEsvc and ENABLEsvc) which removes/
creates the file.
So our developer/programmer are able to disable/enable the backend
server and upload new files,restart service,.. without bother the
requests.
option httpchk HEAD /proxy/proxy-check.php
bye
Bernhard
Matt wrote:
Hi,
I'm currently using a config below. I'd like to be able to drop a
server out of the pool for maintenance, at the moment I am removing
srv1 from the config file and restarting haproxy with the -sf
(reload)
option. Is there a better way I can tell haproxy to stop sending
requests to a server without restarting the binary? Does haproxy
watch the config file and act on certain changes?
Thanks,
Matt
--------------------------------
defaults
mode http
option httplog
option dontlognull
retries 3
redispatch
maxconn 2000
contimeout 5000
clitimeout 50000
srvtimeout 50000
listen rewrite 10.0.0.1:9898
stats enable
stats auth admin:admin
balance roundrobin
server srv1 10.0.0.2 check inter 5000 rise 2 fall 5
server srv2 10.0.0.3 check inter 5000 rise 2 fall 5
