Re: MySQL Server crashes - spawning too many threads.

[Erin ONeill]

Well I'm not sure if my sys admin is blowing me off and I don't have a lot of access to the server... Mytop isn't showing me the queries that are running but it is giving me interesting info. I'm gonna have to see how mytop is configured to start up and play with that one.

I don't see a lot of threads connected and my stats are telling me that too?

I've got thread_cache set to 96. The avg thread connected is 16. Right now I have 94 threads cached but it usually runs between 64-94 threads cached. AND it only runs between 1-3 threads runninng on avg with spikes during busy times.

And yet here is the explaination of why my server was flipped:
The machine isn't crashing. MySQL is spawning too many threads.

So what sort of threads? Actual mysqld threads running? and isn't that controled in the compile? I looked thru my 4.1 mysqld_safe script and saw some interesting stuff about open files that I want to explore but that doesn't seem to be my problem -- or is it?

Meanwhile the sys admin is frothing at the mouth about pconnects & how that's the big problem and my programmers are saying they aren't using them it's hardware. And I'd rather solve my slow query problems! :)

Any thoughts would be appreciated. This isn't covered in any of my optimize books and so far google hasn't brought up anything useful except that I should set interactive_timeout to something low. I set it to 100 and wait_timeout to 15.

Does this sound like hardware to you?? or linux OS or?

erin