|
Hello everyone,
I have a question about ldirectord, we have a maintenance procedure where we
set the real server weight to 0 so connections finish correctly, then we stop
apache on the real server, sleep to let it close all its fcgi, then start the
server, and finally put the weight back to 1.
The problem is when we start the server, ldirectord makes his check, sees the
server is up and so add it back with a weight of 1, 1s later it rereads its
configuration and see that the server should have a weight of 0, so it changes
the weight back to 0.
During this short time period the server takes few thousands request and is not
ready for it, it seems like a bug about the check system.
ldirectord has been upgraded to the latest version available on github, also we
have tested the "maintenacedir" configuration, which behaves the same way as
described above.
Here is the configuration:
# Global Directives
checktimeout=10
checkinterval=5
autoreload=yes
logfile="/var/log/ldirectord.log"
quiescent=yes
fork=yes
maintenancedir = /var/run/ldirectord_maintenance/
virtual=....3:80
real=....72:80 gate
real=....73:80 gate
real=....74:80 gate
real=....75:80 gate
service=http
request="/fcgi-bin/envmy.fcgi"
receive="Mysql table test : OK"
scheduler=rr
protocol=tcp
checktype=negotiate
Do you have any suggestion, any idea ? I have not found any bug related to this.
Thank you all by advance,
Regards,
Jeremy
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
