|
Hi,
> > I am testing a ipvs-0.0.5 VS-DR setup. I have 2 real servers both running
> > 2.4.0-test10
> > (one on RH7.0 and the other RH6.2). I have all three (2 real and
> > director)machines on the same hub on the 10.x.x.x network. Now when I
> > launch
> > testlvs from a machine on 192.168.0.x network, my director and the real
> > server
> > gives me warnings about the ip_conntrack module.
>
> LVS can't work together with ip_conntrack and iptable_nat. There is
> double connection tracking. You still can use ipchains.o and the old
> ipchains binary.
Does this mean, it will not work (because I have LVS and ip_conntrack working
without knowing the above fact)?
So, can I ignore the ip_conntrack errors and continue using lvs(I built
conntrack into the kernel) ?
Since, ip_conntrack is a part of the 2.4 netfilter module, can we use that to
do the connection monitoring rarther than implementing it separtely in lvs?
> But ip_conntrack is working with LVS's connections => big problems.
Any previous experiences that anybody has had with them?
>
> > 2) Does anyone have ideas on why the RH6.2 machine doesnt give me the same
> > error.
>
> More RAM?
yes.
>
> > 3) Not related to the above: How can I calculate the total number of TCP/UDP
> > connections that my cluster can support in VS-DR, and also the number of
> > connections that my realservers can support.
>
> There is "ip_vs" entry in /proc/slabinfo, there is the actual
> size of one connection entry (also displayed on boot). Now divide the
> amount of free RAM on this value. The result is a very optimisitic value
> for the max number of entries you can create in LVS. But you actually
> ask for the ip_conntrack_max limit.
Im sorry, but I looked for help on how to read the slabinfo output, but could
not get any. How do I find the free memory, what do the values in slabinfo
mean. Any pointers on where it is described. Actually, I did want to know the
maximum connections that my lvs can support.
Thanks
Anush
|
