On Thu, 22 Aug 2013, Drunkard Zhang wrote:
> 2013/8/22 Julian Anastasov <ja@xxxxxx>:
> > No kernel options should be related to OPS. I assume
> > you are not using the SH scheduler. Make sure the OPS mode
> > is properly applied to the virtual service, check for "ops"
> > in the configuration:
> > cat /proc/net/ip_vs
> Still no lucky here, ops is set in running config, but it's not like
> that in real world.
> vs3 ~ # cat /proc/net/ip_vs
> IP Virtual Server version 1.2.1 (size=1024)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> UDP 96A46478:0202 wrr ops
> -> 96A46450:0202 Route 25 0 1
The OPS connections are accounted in InActConn
for a very short period, they live up to 1 jiffie, eg. 10ms.
Also, WRR should be reliable for OPS while other
schedulers (eg. *LC) are not suitable.
> And the traffic routed to each realserver didn't following weight I
> set, it's routed pretty much one to one. I got 17 udp sources sending
> to 16 different realservers, the others are bonding to another VIP.
> Prot LocalAddress:Port CPS InPPS OutPPS InBPS OutBPS
> -> RemoteAddress:Port
> UDP x.x.x.120:514 0 67622 0 12339373 0
> -> x.x.x.65:514 0 29 0 2895 0
> -> x.x.x.66:514 0 225 0 21850 0
Do you see the same problem with ipvsadm -Ln --stats ?
ipvsadm -Z may be needed to zero the stats after restoring all
rules. "Conns" counter in stats should be according to WRR
weights, it shows the scheduler decisions.
In your rates listing CPS 0 is confusing, even for OPS.
Is it from the new ipvsadm?
Julian Anastasov <ja@xxxxxx>
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