Details
-
Type:
Task
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Won't Fix
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
This feature dumps every ~20secs the InnoDB engine status on a file on the datadir, on the official MySQL documentation it is documented as "writing periodically the output of SHOW ENGINE INNODB STATUS" without specifying its recurrence.
This startup variable also doesnt have a corresponding runtime variable and it is not possible to configure neither its output filename nor the delay between two dumps and having the ability to activate/deactivate the feature without having to restart the server could also be interresting.
The code that defines the delay between two dumps on 5.5.30 : http://bazaar.launchpad.net/~maria-captains/maria/5.5/view/3749/storage/innobase/srv/srv0srv.c#L2187
Another possibility would be to replace it with a non engine-specific variable as other storage engines might also have engine status inforations (its the case for TokuDB for example) or that could dump informations from P_S/I_S.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Added following new configuration variables:
innodb_monitor_path_and_file
Path and file name for InnoDB monitor output.
User can change this file name on runtime and if file cant be created
default location and name will be used.
innodb_monitor_wait_delay
Minimum delay between two InnoDB monitor outputs to file (15s by
default) and 0 to disable output. User can change this on runtime.
Added more configuration parameters:
innodb_table_monitor_wait_delay
Minimum delay between two InnoDB table monitor outputs to file (60s by
default) and 0 to disable output. User can change this on runtime.
Reason for the decision: InnoDB status output on files will be deprecated because similar output can now be seen from information_schema.
I suppose the documentation part could be done now, and enhancements could go to 10.x if we choose to implement them.