Bug #56266 | MEM my.cnf/my.ini includes event_scheduler = 1 | ||
---|---|---|---|
Submitted: | 25 Aug 2010 18:49 | Modified: | 22 Sep 2010 14:05 |
Reporter: | Andy Bang | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Enterprise Monitor: Installing | Severity: | S3 (Non-critical) |
Version: | 2.2.3.1744 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[25 Aug 2010 18:49]
Andy Bang
[30 Aug 2010 17:22]
Enterprise Tools JIRA Robot
Andy Bang writes: Looks like this was never in 2.1, so it only needs to be removed in 2.2 and 2.3.
[22 Sep 2010 14:05]
Enterprise Tools JIRA Robot
Carsten Segieth writes: Re-open - it is not mentioned in "my.ini_comparison_report.txt" that 'event_scheduler = 1' shall be removed "by hand" after an update from e.g. 2.2.0 to one of the new versions. Also the wording in the comparsion_report.txt looks to me incorrect as 1) there was no migration, the my.cnf is unchanged (compared to it's backup) and 2) it does not show _all_ differences of my.cnf to the recommended config file ("...shows the difference..."). As it is not mentioned in the comparsion_report.txt one has to do a 'diff my-default.cnf my.cnf' to see that there is a no longer recommended option in the current config. How to repeat? -------------- - fresh install 2.2.0.1709 - update to either 2.2.4.1756 or 2.3.0.2024 - check the config files and the comparsion_report.txt ------------------------------------------------------------------------------- < diff my.cnf / my.ini with backup > -rw-rw-r-- 1 qauser qauser 1361 Sep 22 15:18 /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/backup/mysql/my.cnf -rw-rw-r-- 1 qauser qauser 1361 Sep 22 15:18 /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/mysql/my.cnf -rw-rw-r-- 1 qauser qauser 1415 Sep 22 15:25 /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/mysql/my.cnf_comparison_report.txt -rw-rw-r-- 1 qauser qauser 1351 Sep 22 15:25 /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/mysql/my-default.cnf ... diff /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/mysql/my-default.cnf /data0/merlin/monitoring/2.2.0.1709/net-qa1/38080/mysql/my.cnf 27c27 < skip-external-locking --- > skip-locking 30c30 < --- > event_scheduler = 1 ------------------------------------------------------------------------------- < my.ini_comparison_report.txt > MySQL Repository Configuration Report ===================================== This report documents the difference between your existing MySQL configuration file (my.cnf/my.ini) as migrated from your previous Enterprise Monitor installation and our recommended configuration file, which is based on our "Minimum System Requirements" shown at http://mysql.com/support/supportedplatforms/enterprise-monitor.html. The following files were compared: Recommended: my-default.cnf Your file: my.cnf WARNING: Updating your configuration file per our recommendations can help you improve the performance of the Enterprise Monitor, however, much depends on the specifics of your environment (e.g. OS, memory, disk, whether the machine is dedicated to the Monitor or shared with other applications, etc). Please do NOT update your Monitor's configuration file until you thoroughly understand each change and have tested it on a non-production machine. Use the following URL as a starting point to learn more about each parameter: http://dev.mysql.com/doc/refman/5.1/en/server-options.html. Parameter: skip-external-locking Recommended: Your Value: Missing from my.cnf/my.ini Comment: Add for improved performance (turns off use of external file system locking). NOTE: If your configuration file has the skip-locking parameter, note that it has been deprecated and should be renamed to skip-external-locking.