|
On Fri, 2 Jun 2006, Martijn Grendelman wrote:
> I was justing browsing the HOWTO, when I stumbled upon this recent piece of
> text:
>
>
> Apr 2006: No-one has tried this, but it seems that the -SH scheduler could
> replace persistence without the failover problems of persistence. The -SH
> scheduler schedules according to the client IP, meaning that all of a client's
> connection requests will be sent to the same IP. The -SH scheduler has been
> around for a while, but it seems that no-one has known what it did.
>
>
> When I first started to toy around with LVS, I did just what is written here:
> i tried to use the SH scheduler for "session affinity" at L7.
>
> However, I had problems, that I posted to this list:
>
> http://www.in-addr.de/pipermail/lvs-users/2004-March/011171.html
>
> I never found a solution, and I finally decided that SH wasn't going to work,
> and I set up an Msession server for "session clustering" and used the RR
> scheduler. This setup works perfectly and is still in use today.
Looking at your original post from 2004, you are using source hashing with a
weight of 1. This will result in the service being overloaded when the number
of connections is greater than 2, as your output of ipvsadm shows. Have you
tried increasing the weight?
|
