Bug #43427 | Don't limit table_cache_size as a function of max_connections | ||
---|---|---|---|
Submitted: | 5 Mar 2009 17:17 | Modified: | 8 Mar 2009 16:01 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S5 (Performance) |
Version: | 5.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[5 Mar 2009 17:17]
Mark Callaghan
[6 Mar 2009 9:24]
Valeriy Kravchuk
As current behaviour is clearly intended, this is a request for a new feature.
[8 Mar 2009 16:01]
Mark Callaghan
Yes, this is a feature request. MySQL started out as being very tolerant and 'fixing' things quietly. It would be nice to have a mode where it doesn't start or always raises errors instead. While this behavior is intended, the consequences are not. For this particular case, we had a large group of servers get very slow when the open file limit for the mysql user was smaller than we realized.