|
Hello,
On Wed, 6 Jun 2001, Joseph Mack wrote:
> > drop, no memory to allocate connection structure, expect
> > crashes may be at another place (usually user space) :)
>
> It would be nice if the director didn't crash when the number of connections
> got large. Presumably a director would be functioning only as a director and
> the
> amount of memory allocated to user space processes wouldn't change a whole lot
> (ie you'd know how much memory it needed). Is there any way to limit the
> amount
> of memory the ipvs table uses?
I'm not sure what the kernel will decide in this situation but
don't rely on the fact some processes will not be killed :) There is
a constant network activity and a need for memory for
packets (floods/bursts).
And the reason the defense strategies to exist is one: to
free memory for new connections by removing the stalled ones. They
can be automatically activated on memory threshold. Killing the cluster
software on memory presure is not good :)
So, the memory can be controlled, for example, by setting
drop_entry to 1 and tuning amemthresh. On floods it can be increased.
It depends on the network speed too: 100/1000mbit. Thresholds of
16 or 32 megabytes can be used in such situations, of course, when there
are more memory chips :)
> 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
Regards
--
Julian Anastasov <ja@xxxxxx>
|
