|
On Tue, 8 Jun 1999, Wensong Zhang wrote:
> Please tell me more about your VS running ipvs-0.4, so that I can
> repeat the problem.
>
> The insanely huge timeout problem of masquerading entry like the
> incorrect refcnt (Reference Counter) of the masquerading entry.
We're using a standard masq setup with the real servers on a private
network behind the VS. On the VS, we run:
ipchains -F
ipchains -A forward -j MASQ -s 10.0.1.0/24 -d 0/0
ipchains -M -S 5 5 5
ipvsadm -C
ipvsadm -A -t ${vsaddr}:${port} -s wlc
We have mon setup to add/remove the real servers as necessary using:
ipvsadm $cmd -t ${vsaddr}:${port} -r ${addr}:${port} $wstr
Btw, ipvsadm-1.0.0 does not seem to accept any args to -w except -1.
> I have met the other phenonmena.
We were running 2.2.7+0.2 on our primary servers but they were getting
to the point where they required a reboot daily. We've been running
2.2.7+0.4 on our secondary server for about 2 days and one of our
primaries for about a day. Both boxes show the huge timeout problem but
neither seems to have the gradual slowdown problem.
Here's another interesting artifact I came across:
Homer (2.2.7+0.2) just before I rebooted it yesterday with about 6.5 hrs
uptime:
Module Size Used by
ip_vs_rr 992 69 (autoclean)
ip_vs_wlc 10242982 (autoclean)
3c59x 19112 2 (autoclean)
Homer (2.2.7+0.4) now with about 29 hrs uptime:
Module Size Used by
ip_vs_rr 752 4 (autoclean)
ip_vs_wlc 848 1 (autoclean)
3c59x 19112 2 (autoclean)
- cls
|
