|
Ratz wrote:
>
> Hi
>
> <blockquote>
> I think I you're right, I didn't express myself in a clear way. So I
> try
> to explain my problem from another view.
>
> Lets say: I have 1000 http requests (A) through a firewall of a
> customer
> (so in fact all requests have the same Source IP for Loadbalancer,
> because of NAT) and then one request (B) from the Intranet and then
> again 1000 Request (C) from that firewall, what does LB do?
> I have three Realservers r1, r2, r3 (ppc with rr)
>
> a) A to r1, B to r2, C to r1 (because of SourceIP)
> [Distribution:2000:1:0.0000001]
> b) A to r1, B to r2, C to r3 (because r3 is free)
> [Distribution:1000:1:1000]
> c) A to r1, B to r2, C to r2 (due to the low load of r2)
> [Distribution:1000:1000:0.000001]
> c) A to r1 && r2 && r3 (depending on source port), B to r1 || r2 || r3,
> C to r1 && r2 && r3 [Distribution: 667:667:666]
>
If C reachs the load balancer before all the 1000 requests
of A expire, then the requests of C will be sent to r1,
and the distribution is 2000:1:0.
If all the requests of A expires, the requests of C will
be forwarded to a server that is selected by a scheduler.
BTW, persistent port is used to solve the connection
affinity problem, but it may lead to dynamic load
imbalance among servers.
> Please tell me if I'm writing off-topic or if it seems that I really
> didn't understand ppc-scheduling. I would also be very happy, if
> someone
> could draw some flowchart or a sketch of the different scheduler
> working. I'd do it, if I am sure having understood the concept
> properly.
>
> Another stupid question is:
> Is the dport used? If I enter following sequence:
which dport do you mention?
>
> ipvsadm -A -t 172.23.1.100:80 -s rr -p
> ipvsadm -A -t 172.23.2.100:80 -s wrr
> ipvsadm -a -t 172.23.1.100:80 -r 172.23.1.1:8080 -g -w 1
> ipvsadm -a -t 172.23.1.100:80 -r 172.23.1.2:8080 -g -w 1
> ipvsadm -a -t 172.23.2.100:80 -r 172.23.2.1:8007 -g -w 2
> ipvsadm -a -t 172.23.2.100:80 -r 172.23.2.2:8011 -g -w 3
> ipvsadm -L
>
> IP Virtual Server version 0.8.2 (size=65536)
> Protocol LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 172.23.2.100:80 wrr
> -> 172.23.2.2:80 Route 3 0 0
> -> 172.23.2.1:80 Route 2 0 0
> TCP 172.23.1.100:80 rr persistent
> -> 172.23.1.2:80 Route 1 0 0
> -> 172.23.1.1:80 Route 1 0 0
>
> Where are my dports or did I misunderstand something completely?
>
> Thankx go out to you all, specially to Wensong for writing this stuff.
>
> ratz. (Roberto Nibali)
>
> </blockquote>
>
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
