Not sure what is going on, but the version of MySQL you are using is
ancient. The current version of MySQL is 5.0.37. Even MySQL 4.1 (which
has been end-of-lifed) has a latest version of 4.1.22. If it is a bug
you are seeing, it likely has been fixed in a later version.
Cheers,
Jay
Kishore Jalleda wrote:
Hello Everybody,
I increased the query_cache_size on one of our
main servers from 100 MB to 250 MB, since I was seeing a very high rate lot
of Qcache Low Mem prunes. The server was fine for 15 minutes and the Low
mem
prunes went down to almost zero, but then started getting too many
connections errors and the queries were taking too long to execute, and
only
after the roll backed the change the server started behaving normally. This
could not be a co-incidence as the server has been running fine for months
even under heavy traffic conditions.
Has anybody ever experienced such a thing or
know what could be the cause ..
Server info
4.1.11-Debian_4sarge3-log
32GB RAM
Max_connections : 400
Thanks
Kishore Jalleda
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
