|
On Thu, Dec 29, 2005 at 05:13:21PM +0100, Roberto Nibali wrote:
> Hello,
>
> The following two patches (kernel space and user space man page fixes)
> address the 3/4 threshold cut-off when lower threshold is not set.
>
> diff-tree fdb7185... (from bc22290...)
> Author: Roberto Nibali <ratz@xxxxxxxxxxxxxxxxxxxx>
> Date: Thu Dec 29 17:00:04 2005 +0100
>
> [IPVS]: Remove 3/4 threshold cut-off when the lower threshold is
> not set
>
> There is no reason to change the semantics of upper and lower threshold
> handling when the lower threshold limit is not set (meaning 0). The
> original
> semantics to re-introduce a real server as soon as the lower
> threshold limit
> is hit with the connection counter should apply generally. This
> patch revert
> the original semantics to a more intuitive one.
>
> Signed-off-by: Roberto Nibali <ratz@xxxxxxxxxxxx>
>
> Please consider applying,
> Roberto Nibali, ratz
Doesn't mean that if the lower threshold isn't set, then the
number of connections needs to drop to 0 before an overloaded
real server will be marked as un-overloaded.
While I think the simplicity of your approach makes a lot of sense.
I also think it makes a lot of sense for users to just specify
the upper threshold and have something sensible happen, which
to my mind is something like the current 3/4 rule.
--
Horms
|
