On Wed, Nov 01, 2000 at 11:10:46AM -0600, matthew wrote:
> On Wed, 1 Nov 2000, Sean Hunter wrote:
>
> > Pardon my speculations (if I am wrong), but isn't this an oracle question?
>
>
> It could be.
>
>
> > Isn't oracle killing the server by trying to clean up 1800 connections all at
> > once? When they're all connected, most of the work is done by one or two
> > oracle processes, but when you kill your ddos thing, all of the oracle
> > listeners (of which there is one per connection), steam in and try to clean up.
>
>
> Yes, but the factor that drove me to the list was that it's been > 400
> load average for 10 hours now. Even if Oracle tried to clean up 1800
> connections at once, would it take this long? That's not rhetorical, as
> the answer may well be "yes".
>
Yup. What seems to have happened is that waking up 1800 processes at once has
caused the box to thrash so hard it is taking ages for any one process to get
enough scheduler time to clean itself up and exit.
I guess we may need a thrash preventer that slows things down enough for each
process to get a healthy bite of the cherry.
Sean
>
> > I thought oracle had an internal connection limit (on our servers it is set to
> > 440 connections), anyways.
>
>
> This is set in the init.ora. I jacked it up to allow > 2000 connections.
>
> Matthew
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
