On Thu, 8 Apr 2004, Randy Paries wrote:
> Now if I take down the http server on krusty and do a ipvsadm --list I get
> ipvsadm --list
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> -> local.krusty:http Route 0 0 0
>
> But If I try to go to the web server I get page not found. But if I restart
> ldirectord
> Krusty is no longer listed and I now go to flanders successfully.
I guess that would be desirable behaviour. You didn't include
ldirectord.cf, but you probably have quiescent=yes in it. From the
manpage:
quiescent = [yes|no]
If yes, then when real or failback servers are determined to be down,
they are not actually removed from the kernel's LVS table. Rather,
their weight is set to zero which means that no new connections will be
accepted. This has the side effect, that if the real server has persis-
tent connections, new connections from any existing clients will con-
tinue to be routed to the real server, until the persistant timeout can
expire. See ipvsadm for more information on persistant connections.
If you restart ldirectord, there's no point in adding services to the LVS
table which are not working.
Willem
|