Reposted from my NG post, I'm hoping someone can help out, this is getting ugly. The problem I am describing is happenning in less than 24 hours now. As volume increases the period is getting shorter.
I'm hoping someone can help me, I've got a problem with mysql going insane.. I've a quite busy application (avg 700 queries a second right now) - with about 40 odd seperate databases (scalability requirement) Anyway, depending on volume of transactions, it seems to go insane. I am using a mix of InnoDB for the important tables, and MyISAM for the raw data tables. After a while, one of my queries that uses RAND() as an order by simply stops returning any rows, either in the script that's calling it or the mysql shell. Remove the RAND() and it works fine. Then shortly after that, it fails altogether, and I have to kill a mysqld process that's hung and restart. This is on a FreeBSD 4.7 system, with 2gigs of ram. Restarting seems to fix it, so I have to assume that something's leaking. Can php cause mysql to leak resources? I dunno what's going on here, but the script is going to get substantially busier and I don't wanna have to be restarting this damn thing every few hours. Any help? I'll be quite happy to provide any information needed, but the system is currently running, so I can't be too crazy with it, I'd like to be able to diagnose and/or fix the problem without too much (or any) downtime. Cheers, Jason --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
