|
Hi Joe,
> It would be nice if the director didn't crash when the number of connections
> got large.
I don't exactly know where there is the misunderstanding but the director
never crashes because of exhaustion of memory. If he tries to allocate
memory for a new entry into the table and kmalloc returns NULL, we return,
or better drop the packet in processing and generate a page fault.
> 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?
Not that I would know of but you could use my treshold limitation patch :)
Then you calculate how many connections you can sustain with your memory
by multiplying each connection entry with 128bytes and divide by the amount
of realserver and set the limitation alike. Example:
128MByte, persistency 300s: max amount of concurrent connections: 3495.
We assume having 4 realservers equally load balance, thus we have to
limit the upper threshold per realserver to 873. Like this you would never
have a memory problem but a security problem.
Best regards,
Roberto Nibali, ratz
--
mailto: `echo NrOatSz@xxxxxxxxx | sed 's/[NOSPAM]//g'`
|
