Steven,
Have you tried switching to weighted least connection scheduler ?
scheduler=wlc
This might be more suitable for your application.
Regards
__________________________________________
Dean Manners
> -----Original Message-----
> From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:lvs-users-
> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Steven Truong
> Sent: Saturday, 2 February 2008 09:33
> To: LinuxVirtualServer.org users mailing list.
> Subject: [lvs-users] Unbalanced master node with Ultramonkey
>
> Dear, all. I just set up Ultramonkey streamline HA LB for my 2
> openldap servers.
>
> virtual=192.168.100.15:389
> real=192.168.100.16:389 gate
> real=192.168.100.14:389 gate
> fallback=127.0.0.1:389
> service=ldap
> scheduler="rr"
> protocol=tcp
> checktype=negotiate
> checkport=386
> .....
>
>
> However, one of the real servers (100.14) keep consistently becoming
> the master node of the two nodes. When both nodes are running, then
> this node would always be the master.
>
> Is there anyway that I can change to give the other node to become
> master while both are running? Weight or change the scheduler???
>
> Please suggest ways to do this.
>
> Thank you.
> Steven.
>
> _______________________________________________
> 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
|