|
>
> (Yep, assuming the same thing you're referring to are the instructions
> in the FAQ about increasing "file-max" and "inode-max" via the procfs
> interface.)
>
> > No-one has talked about changing any of these values on this list.
> > Presumably it's not a problem for most people.
>
> That scares me. :)
>
> Then either we're "the special case" for which it all just breaks,
> nobody else is running LVS with lots of servers which would require
> increasing file-max or inode-max, or we're pushing the limits of what
> the code is capable, which makes me sad since it really isn't doing all
> that much...
It's not easy being out in front :-)
I don't think many people are using VS-NAT for heavy duty LVS serving.
Most are using VS-DR. However the real-servers don't really know whether
they are in a VS-NAT or VS-DR LVS.
You are changing the settings on the real-servers and not the director?
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
