Bug #70213 | INFORMATION_SCHEMA.innodb_metrics documentation incomplete | ||
---|---|---|---|
Submitted: | 2 Sep 2013 10:52 | Modified: | 19 Nov 2013 18:25 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6.13,5.7.1 | OS: | Any |
Assigned to: | Daniel Price | CPU Architecture: | Any |
[2 Sep 2013 10:52]
Simon Mudd
[2 Sep 2013 11:28]
MySQL Verification Team
Thank you for the bug report.
[2 Sep 2013 15:14]
Simon Mudd
So I've just checked (5.6.13) what happens with a few different settings in /etc/my.cnf # this works innodb_monitor_enable = module_log,metadata_table_handles_opened,metadata_table_handles_closed # this does not work - only the last entry is actually enabled (5.6.13) innodb_monitor_enable = module_log innodb_monitor_enable = metadata_table_handles_opened innodb_monitor_enable = metadata_table_handles_closed The latter of course is inconsistent with: [root@myhost-01 ~]# grep repl /etc/my.cnf replicate-wild-do-table = mysql.% replicate-wild-do-table = mydb.% [root@myhost-01 ~]# So good clear documentation would be helpful here to avoid confusion and mistakes.
[2 Sep 2013 15:16]
Simon Mudd
Compare again to the same server's P_S configuration: {noformat} [root@myhost-01 ~]# grep perfor /etc/my.cnf performance_schema = 1 # performance_schema.setup_consumers begin performance_schema_consumer_events_waits_current = ON performance_schema_consumer_events_waits_history = ON # performance_schema.setup_consumers end
[2 Sep 2013 16:05]
Jon Stephens
Discussed with Andrii, assigning to myself since Paul's currently unavailable.
[19 Nov 2013 18:25]
Daniel Price
Thank you for the bug report. Unfortunately, we are not able to address every request but here's what's been done: (1) Information has been added outlining the semantics for enabling counters using the my.cnf file. (2) The "inconsistent" semantics are "as designed" but the nuisance of semantics that differ from performance_schema semantics, for example, has been noted by the MySQL Development team. (3) The MySQL Development team has noted the request to refrain from changing or deleting counters in minor releases and will avoid doing so. New counter additions will continue to occur in any release, as new features and functionality are added. (4) Related documentation updates: * Expanded examples * An updated list of counters (note that counters may differ by platform). * A recommendation has been added to check release notes and review the innodb_metrics table for new releases prior to upgrading. * Information regarding why some counters are enabled by default (Counters that are enabled by default correspond to those used by SHOW ENGINE INNODB STATUS.) Documentation changes should show up in the next day or so.