Bug #57804 enabling monitor counter from my.cnf
Submitted: 28 Oct 2010 12:21 Modified: 20 Dec 2013 12:58
Reporter: Jimmy Yang Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: Jimmy Yang CPU Architecture:Any

[28 Oct 2010 12:21] Jimmy Yang
Description:
Currently, we cannot set monitor counter from my.cnf does not activate the counters. This bug is filed to support such:

We do not process the variable's corresponding global variable innobase_enable_monitor_counter during server startup in innobase_init(). So specify this in the my.cnf will have no effect on the variable.

The reason has been that we think this is a variable that would always be off by default, and user uses "set global innodb_enable(/disable/reset/reset_all)_monitor_counter" to turn on/off it.  So all of these system variables can be set during run time at command line.

However, said that, innodb_enable_monitor_counter might be a bit special, as in your case, users might want to turn it (a group) on by default. I can add this support.

How to repeat:
feature request
[28 Oct 2010 12:29] Calvin Sun
Workaround is to use SET after server startup.
[22 Dec 2010 21:30] Bugs System
Pushed into mysql-trunk 5.6.1 (revid:alexander.nozdrin@oracle.com-20101222212842-y0t3ibtd32wd9qaw) (version source revid:alexander.nozdrin@oracle.com-20101222212842-y0t3ibtd32wd9qaw) (merge vers: 5.6.1) (pib:24)
[20 Dec 2013 12:58] Erlend Dahl
Fixed in 5.6.2.