On Sat, 24 Aug 2013, Drunkard Zhang wrote:
> > May be we can enable debug for short time when
> > OPS is not working:
> > # Start debug for 10ms
> > echo 20 > /proc/sys/net/ipv4/vs/debug_level
> > usleep 10000
> > # Stop debug
> > echo 0 > /proc/sys/net/ipv4/vs/debug_level
> > You can show me such debug. The main thing to
> > understand is where in IPVS the traffic is lost, the
> > debug will be helpful, it should be no more than one
> > page per packet. I need debug for one packet, something
> > that you see is repeated in logs. May be due to the
> > destination trash mechanism something is not set properly
> > after the ipvsadm -C && ipvsadm -R sequence.
> I'll provide those test result later.
> So, about debug, do you mean when I find OPS is not working, then
> cutoff the traffic, turn on debug with "echo 20 >
> /proc/sys/net/ipv4/vs/debug_level", and then emulate the traffic with
> a couple of packets, like this?
> logger -d -n $VIP "hello, this is test"
> Or, should I just enable debug for tiny time slice under high traffic?
Whatever is your preference, it does not matter
for me. With traffic you risk to flood log in director,
for 10ms we get ~600 packets. I think, even usleep 1000
will work. And I'm not sure what will happen when many
CPUs write to log. If you stop the traffic and send just
one message under debug it would be more safe, if it is not
a problem that your service is not available for some seconds.
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