Le jeudi 22 juillet 2010 à 07:51 +0400, Franchoze Eric a écrit :
> I'm trying to do load balancing of incoming traffic to my applications. This
> applications are not very smp friendly, and I want try to run some instances
> according to number of cpus on single machine. And balance load of incoming
> traffic/connections to this applications.
> Looks like is should be similar to
> linux kernel 2.6.32 with or without hide interface patches. Tried
> different configurations but could not see packets on application layer.
> 192.168.1.165 - eth0 - interface for external connections
> 188.8.131.52 - dummy0 - virtual interface, real application is binded to that
> Configuration is:
> -A -t 192.168.1.165:1234 -s wlc
> -a -t 192.168.1.165:1234 -r 184.108.40.206:1234 -g -w
> #ipvsadm -L -n
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 192.168.1.165:1234 wlc
> -> 220.127.116.11:1234 Local 1 0 0
> [ 2106.897409] IPVS: lookup/out TCP 192.168.1.165:44847->192.168.1.165:1234
> not hit
> [ 2106.897412] IPVS: lookup service: fwm 0 TCP 192.168.1.165:1234 hit
> [ 2106.897414] IPVS: ip_vs_wlc_schedule(): Scheduling...
> [ 2106.897416] IPVS: WLC: server 18.104.22.168:1234 activeconns 0 refcnt 2 weight
> 1 overhead 1
> [ 2106.897418] IPVS: Enter: ip_vs_conn_new, net/netfilter/ipvs/ip_vs_conn.c
> line 693
> [ 2106.897421] IPVS: Bind-dest TCP c:192.168.1.165:44847 v:192.168.1.165:1234
> d:22.214.171.124:1234 fwd:L s:0 conn->flags:181 conn->refcnt:1 dest->refcnt:3
> [ 2106.897425] IPVS: Schedule fwd:L c:192.168.1.165:44847
> v:192.168.1.165:1234 d:126.96.36.199:1234 conn->flags:1C1 conn->refcnt:2
> [ 2106.897429] IPVS: TCP input [S...] 188.8.131.52:1234->192.168.1.165:44847
> state: NONE->SYN_RECV conn->refcnt:2
> [ 2106.897431] IPVS: Enter: ip_vs_null_xmit, net/netfilter/ipvs/ip_vs_xmit.c
> line 212
> [ 2106.897439] IPVS: lookup/in TCP 192.168.1.165:1234->192.168.1.165:44847
> not hit
> [ 2106.897441] IPVS: lookup/out TCP 192.168.1.165:1234->192.168.1.165:44847
> not hit
> [ 2107.277535] IPVS: packet type=1 proto=17 daddr=255.255.255.255 ignored
> [ 2108.542691] IPVS: packet type=1 proto=17 daddr=192.168.1.255 ignored
> As the result, server application does receive anything on accept(). I tried
> to make dummy0 a hidden device and play with arp settings. But without result.
> I will be happy to hear any idea how to do connection in this environment.
lvs seems not very SMP friendly and a bit complex.
I would use an iptables setup and a slighly modified REDIRECT target
(and/or a nf_nat_setup_info() change)
Say you have 8 daemons listening on different ports (1000 to 1007)
iptables -t nat -A PREROUTING -p tcp --dport 1234 -j REDIRECT --rxhash-dist
rxhash would be provided by RPS on recent kernels or locally computed if
not already provided by core network (or old kernel)
This rule would be triggered only at connection establishment.
conntracking take care of following packets and is SMP friendly.
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html