|
Is this a bug or a feature of the PCC scheduling...
A person connects to the virtual server, gets direct routed to a machine.
Before the time set to expire persistent connections, that real machine
dies. mon sees that the machine died, and deletes the real server entries
until it comes back up.
But now that same person tries to connect to the virtual server again, and
PCC *STILL* schedules them for the non-existent real server that is
currently down. Is that a feature? I mean -- I can see how it would be good
for small outages... so that a machine could come back up really quick and
keep serving its old requests... YET... For long outages those particular
people will have no luck.
? Bug or feature?
All the best --
Ted
----- Original Message -----
From: Wensong Zhang <wensong@xxxxxxxxxxxx>
To: <linux-virtualserver@xxxxxxxxxxxx>
Cc: Ted Pavlic <tpavlic@xxxxxxxxxxx>
Sent: Friday, July 09, 1999 10:56 AM
Subject: ipvs-0.7 for kernel 2.2.10 released
>
> Hi,
>
> The virtual server patch v0.7 for kernel 2.2.10 is now available at
> http://proxy.iinchina.net/~wensong/ippfvs/ipvs-0.7-2.2.10.tar.gz
>
> The changes are as follows:
> Changes:
> - Added a separate masq hash table for IPVS.
>
> - Added slow timers to expire masq entries.
> Slow timers are checked in one second by default. Most overhead
> of cascading timers is avoided.
>
> With this new hash table and slow timers, the system can hold
> huge number of masq entries, but make sure that you have
> enough free memory. One masq entry costs 128 bytes memory
> effectively (Thank Alan Cox), if your box holds 1 million masq
> entries (it means that your box can receive 2000 connections per
> second if masq expire time is 500 seconds in average.), make sure
> that you have 128M free memory. And, thank Alan for suggesting
> the early random drop algorithm for masq entries that prevents
> the system from running out of memory, I will design and implement
> this feature in the near future.
>
> - Fixed the unlocking bug in the ip_vs_del_dest().
> Thank Ted Pavlic <tpavlic@xxxxxxxxxxx> for reporting it.
>
>
> Enjoy,
>
> Wensong
>
>
>
|
