table_open_cache and table_definition_cache testcases fail on systems with low ulimit -n
|Percona Server||Status tracked in 5.6|
[7 Jun 7:04] Laurynas Biveinis
5.6.12 appears to change table_open_cache default from 2000 to 431 and table_definitio
This is not documented, makes 4 MTR tests fail consistently (don't you see it in your runs?), and probably was not intended.
Probably a side effect of the commit below, which says nothing about changing the defaults.
$ bzr log -r 4948
committer: Marc Alff <email address hidden>
branch nick: mysql-5.6-bug16430532
timestamp: Fri 2013-03-22 20:12:50 +0100
Bug#16430532 WRONG SIZING HINTS USED IN THE PERFORMANCE SCHEMA
Before this fix, the server did perform the following actions during
Retrieve the value of
from the user configuration provided in my.cnf,
and use this settings as a base to compute
Then, later in the startup process:
- max_connections could be trimmed down
- open_files_limit could be either computed (replacing the 0 value) or
Because of the order used, the performance schema automated sizing
was based on incorrect data.
With this fix, the server startup code has been changed to perform part 2)
first, and only when all the proper sizing parameters are finally computed
and adjusted, then perform the performance schema initialization in part 1)
Also, the code performing 2) has been cleaned up to be maintainable.
Clarity in this complicated process (due to related dependencies between
configuration settings) is critical here.
How to repeat:
So the difference between 5.6.11 and 5.6.12 is that 5.6.11 adjusts max connections and table cache size only if open_files_limit == 0, and 5.6.12 does that unconditionally.
- Undocumented and untested table_open_cache table_definition_cache
- default change
+ table_open_cache and table_definition_cache testcases fail on systems
+ with low ulimit -n
|no longer affects:||mysql-server|