Bug #58121 | different MySQL behavior while using open_files_limit vs open-files-limit my.cnf | ||
---|---|---|---|
Submitted: | 10 Nov 2010 17:01 | Modified: | 11 Nov 2010 16:42 |
Reporter: | DBA Lead | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.0/5.1 | OS: | Linux (CentOS/Debian) |
Assigned to: | CPU Architecture: | Any | |
Tags: | MySQL, open files |
[10 Nov 2010 17:01]
DBA Lead
[10 Nov 2010 17:07]
Valeriy Kravchuk
Please, upload the entire my.cnf. I wonder what section open_files_limit is used at ([mysqld] or [mysqld_safe])...
[10 Nov 2010 17:14]
DBA Lead
[mysqld] in both cases.
[10 Nov 2010 18:39]
Valeriy Kravchuk
What exact versions, 5.0.x and 5.1.y, are we talking about? Check bug #47095.
[10 Nov 2010 18:50]
DBA Lead
5.1.45 and 5.0.51a-24 So what exactly is the difference b/w '_' and '-' in variable/option names. Shouldn't they be the same thing as mentioned on the web page I shared above? Please explain. Thanks.
[11 Nov 2010 4:19]
Valeriy Kravchuk
We had the problem with open_files_limit as you can conclude from bug #47095. Only version with '-' was taken into account. It was a bug. Please, check if the problem is repeatable with a recent version, 5.1.52.
[11 Nov 2010 16:32]
DBA Lead
you are right using open_files_limit and open-files-limit both have the same affect in mysql 5.1.52. Thanks.
[11 Nov 2010 16:42]
Valeriy Kravchuk
Not repeatable with 5.1.52.
[1 Dec 2010 7:17]
Arjen Lentz
This sounds like a dup of http://bugs.mysql.com/40368 If you read that bug (as I reported), it's visual behaviour is very confusing and can easily lead to incorrect conclusions. However, the bug was there, can be verified, and was addressed in 5.0 OurDelta, MariaDB, and MySQL 5.5