|
Hello all,
It seems there is a problem with the SH scheduler and local node feature.
I configured my LVS director (node-102) in direct routing mode on a 2.4.18 linux
kernel with ipvs 1.0.2. The realservers are set up accordingly.
root@node-102# ipvsadm --version
ipvsadm v1.20 2001/11/04 (compiled with popt and IPVS v1.0.2)
root@node-102# ipvsadm -Ln
IP Virtual Server version 1.0.2 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.0.50:23 sh
-> 192.168.32.103:23 Route 1 0 0
-> 192.168.32.101:23 Route 1 0 0
With this configuration, it's ok. Connections from different clients are
load-balanced on both servers.
Now I add the director:
root@node-102# ipvsadm -Ln
IP Virtual Server version 1.0.2 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.0.50:23 sh
-> 127.0.0.1 Route 1 0 0
-> 192.168.32.103:23 Route 1 0 0
-> 192.168.32.101:23 Route 1 0 0
All new connections whatever the client's IP goes to the director.
And with this config:
root@node-102# ipvsadm -Ln
IP Virtual Server version 1.0.2 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.0.50:23 sh
-> 192.168.32.103:23 Route 1 0 0
-> 192.168.32.101:23 Route 1 0 0
-> 127.0.0.1
Now all new connections whatever the client's IP goes to node-103.
So it seems that with localnode feature, the scheduler always choose the
first entry in the redirection rules.
Did I miss something ?
Thanks in advance for your help.
--
Rached Ben Mustapha | Alinka Cluster Solutions
Software Developer | http://www.alinka.com/
rached@xxxxxxxxxx | +33 1 49 96 46 46
|
