|
On 5 May 2010 08:22, Simon Horman <horms@xxxxxxxxxxxx> wrote:
> On Tue, May 04, 2010 at 08:38:35PM +0100, Malcolm Turnbull wrote:
>> We seem to be hitting this error when load testing an LVS based box
>> with the latest kernel:
>>
>> @@ -191,6 +193,8 @@ ip_vs_wrr_schedule(struct ip_vs_service
>> /* back to the start, and no dest is found.
>> It is only possible when all dests are OVERLOADED */
>> dest = NULL;
>> + IP_VS_ERR_RL("WRR: no destination available: "
>> + "all destinations are overloaded\n");
>> goto out;
>>
>> How does LVS define overloaded?
>
> Hi Malcolm,
>
> I just checked through the code and the IP_VS_DEST_F_OVERLOAD flag of
> a real-server is set if the number of connections exceeds the preset
> upper-threshold. And is cleared once the number of connections drops
> below the lower-threshold.
>
>
>
> Getting OPS upstream is on my todo list. So if you have a patch
> then I'm very interested in it.
>
>
Simon,
Thanks , pretty sure this was now a mis-communication with the testing
team and it was actually because all of the servers had gone offline
and no backup was present!
Nick will be in touch with our OPS patch
--
Regards,
Malcolm Turnbull.
Loadbalancer.org Ltd.
Phone: +44 (0)870 443 8779
http://www.loadbalancer.org/
_______________________________________________
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
|
