Re: mysql max_connections
Posted by:
Rick James
Date: December 12, 2009 03:56PM
When you hit max_connections... Existing connections continue to run. New connections will fail when trying to connect; they are not queued up. When a connection disconnects (or is disconnected due to wait_timeout), there will be a 'thread' available for some future connection.
The issue is connections, not write queries or read queries.
Your code should check for errors after connecting, after reading, after writing, etc. Otherwise, some errors may go unnoticed for a long time.
Which buffer size? key_buffer_size? This is used only for MyISAM index blocks. It has a hard limit of 4GB in 4.1, and even in earlier versions of 5.x. The recommended value (for a MyISAM-only setup) is about 20% of available RAM. There are few systems (yet) that need more than 4GB for the key_buffer. How much RAM do you have?
Subject
Written By
Posted
December 11, 2009 01:26AM
Re: mysql max_connections
December 12, 2009 03:56PM
December 16, 2009 11:59PM
December 17, 2009 12:39AM
December 20, 2009 11:39PM
December 22, 2009 12:37AM
December 24, 2009 02:01PM
December 25, 2009 12:49AM
December 25, 2009 03:30AM
December 25, 2009 03:49AM
December 25, 2009 11:12PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.