We've just switched from compiling our own MySQL to using your binary
distribution. This is the first time we've run MySQL in production from
one of your binary builds. We had to switch to a binary distribution
because we were running into the 1000 threads issue with the GLIBC
library we were linking against.
We've now had the server running for about a week and we've just run
into a little problem which seems like it's a bug in the mysql and
mysqladmin client, or a problem with the mysqld server.
We currently have ~1117 clients connected to our production database,
all of these connections are TCP/IP based connections, none of them are
on the local domainsocket on the db server.
Our DB server was taking a pounding, so I logged into the db server,
and connected as root and tried to list the connected processes:
---
db-01:~> mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 49923 to server version: 3.23.43-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> show processlist;
ERROR 2013: Lost connection to MySQL server during query
---
Ooops! The thread died! Tried again, doesn't work, tried mysqladmin -u
root -p processlist, same deal! Crashed thread! Nothing appears in the
mysql error log.. I tried running some queries on one of our databases
from the db server using the mysql client. If I do a select * on a
table with only a few rows (seems like less then 100), the query goes
through fine. If I do it on a table with more then like 100 rows, the
thread crashes:
mysql> select * from Course;
[.....]
74 rows in set (0.00 sec)
mysql> select * from Section;
ERROR 2013: Lost connection to MySQL server during query
mysql> select count(*) from Section;
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 49927
Current database: TT_fcgi
+----------+
| count(*) |
+----------+
| 318 |
+----------+
1 row in set (0.11 sec)
mysql>
----
Is there something horrifically wrong with mysql when it goes over 1000
connections or something? I swear I was able to do "show processlist"
from the db server yesterday (but we had less then 1000 connections
yesterday). I *am* able to a process list if I connect through TCP/IP:
db-01:~> mysql -u joe -h 127.0.0.1 -p
So it looks like it just effects the domain socket connections, and
TCP/IP is okay. Fortunaetly all of our apps use TCP/IP, so it's not a
big deal to us. But I bet somebody out there -does- care! :) The
threads crashing seems to compeltely uneffect any of our TCP/IP
connections running queries at the same time.
Thanks,
-Joe
---------------------------------------------------------------------
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
