Bug #71821 | Manual doesn't explain that max_connections is "autosized" when ulimit -n is low | ||
---|---|---|---|
Submitted: | 24 Feb 2014 17:58 | Modified: | 14 Mar 2014 14:19 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | autosized, max_connections, ulimit |
[24 Feb 2014 17:58]
Valeriy Kravchuk
[25 Feb 2014 11:17]
MySQL Verification Team
Hello Valeriy, Thank you for the bug report. Thanks, Umesh
[14 Mar 2014 1:23]
James Day
I agree that the manual should say which variables are auto-reduced if the required open_files_limit needed for them can't be obtained. We're not keen on giving the exact rules because those could change. James Day, MySQL Senior Principal Support Engineer, Oracle
[14 Mar 2014 14:19]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly. I'll mention that the server reduces the value of max_connections if the required number of file descriptors is unavailable. Specific details on autosizing can change so they aren't given.