Bug #66912 | Maximum value for open-files-limit | ||
---|---|---|---|
Submitted: | 21 Sep 2012 15:28 | Modified: | 14 Jan 2013 19:48 |
Reporter: | Emilie B | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
Version: | 5.6.6 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[21 Sep 2012 15:28]
Emilie B
[21 Sep 2012 16:06]
MySQL Verification Team
Thank you for the bug report. Did you read in the Manual (same place you pointed)? "mysqld may attempt to allocate more than the requested number of descriptors (if they are available), using the values of max_connections and table_open_cache to estimate whether more descriptors will be needed." Thanks.
[24 Sep 2012 8:16]
Emilie B
Yes, I read the manual. On my server, I have table_open_cache = 400 and max_connections = 800 If I do nothing open_files_limit = 6048. If I change it in my.ini to increase it always add 2048 to my value. For example if I add open_files_limit = 10000 in my.ini , the show variables shows 12048. And if I try whith 65535, it becomes 67583 which is more than the maximum value and looks strange to me ...
[14 Dec 2012 19:48]
Sveta Smirnova
Thank you for the feedback. This looks like not a bug for me: 65535 is maximum permitted value if set manually, not maximum number of descriptors which MySQL can open. Regarding to number 2048, what are default operating system limits for the user you run mysqld as?
[15 Jan 2013 1:00]
Bugs System
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".