MySQL Bugs: #53369: Works with max_connection=10000, but dont work with max

Bug #53369	Works with max_connection=10000, but dont work with max_connection=1000
Submitted:	3 May 2010 11:59	Modified:	3 Jun 2010 14:31
Reporter:	Jeff King	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.77	OS:	Linux (CentOS-5.3)
Assigned to:		CPU Architecture:	Any

Description:
Mysqld crash on high load then max_connection=1000 or max_connection=5000, but all works fine with max_connection=10000. The real number of connection is about 300. Database engine InnoDB. OS - CentOS 5.4. Sometimes Mysqld totally crash. Sometimes just crash on existing connection with 

PHP Warning: mysql_pconnect(): Link to server lost, unable to reconnect

but on the over connection in same time works fine.

my.cnf 

[mysqld]
#innodb_force_recovery=6
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
max_connections=10000
max_allowed_packet=512M
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
innodb_buffer_pool_size=1024M
log-slow-queries=/var/log/mysql/mysql-slow.log
long_query_time=1
#log-queries-not-using-indexes
tmp_table_size=128M
key_buffer_size=512M
table_cache=512
sort_buffer_size=32M

How to repeat:
High load (~300 connections) on Mysqld

Thank you for the bug report. Could you please upgrade to last release 5.0.90? If you continue with the crash please provide a backtrace. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".