|
Hi Julian,
I see, it should be network related. May be we have to
extend this message to see what data (protos, ports, types, codes)
contains this message. Can someone try patch and for what IPVS,
I can provide such one.
Unfortunately this doesn't happen to me, but maybe Alex Kramakov would
be willing to test it.
2688 are too many, the routing cache should be tuned
in this way (/proc/sys/net/ipv4/neigh/default/):
gc_thresh2 > 2688 (more than hosts on the LAN), 4096?
gc_thresh3 > gc_thresh2
I need to check back with the code to find out which means what. Hey,
what about extending LVS to have a total count of active RIPs and to
check if gc_tresh* is too low an raise it accordingly? This would be
nice, not?
As for /proc/sys/net/ipv4/route:
max_size should be increased enough not to lead to failed
routes.
Yup, forget about that one. But normally this is high enough, not? Also
it is truely complex to understand what influence each value in
/proc/sys/net/ipv4/{neigh|route}/* have to the system.
As for the free memory problems, whether ip_dst_cache in /proc/slabinfo
shows big number for current/max conns (1st/2nd column)?
As you can see from various postings from him, it doesn't seem to be a
problem.
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
|
