Bug #33528 Please change the word on the innodb Advisor rule.
Submitted: 27 Dec 2007 7:09 Modified: 28 Jul 2009 10:56
Reporter: Mikiya Okuno Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:1.3.0.8637 OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[27 Dec 2007 7:09] Mikiya Okuno
Description:
InnoDB log file acts like redo logs, but the MySQL Reference Manual doesn't say so but says simply "Innodb log".

Please change the word from "InnoDB Redo Logs" to "InnoDB Logs".

As well as English, please change the word from "InnoDB再実行ログ" to "InnoDBログ
" in Japanese locale.

How to repeat:
Look at the "InnoDB Redo Logs Not Sized Correctly" advisor rule.
[16 Jul 2009 11:00] Mark Leith
Please change to "InnoDB Transaction Log" rather than "InnoDB Log" - they are commonly referred to mostly as "Transaction Logs".
[24 Jul 2009 17:44] Enterprise Tools JIRA Robot
Andy Bang writes: 
Committed revision 286.
[24 Jul 2009 23:44] Enterprise Tools JIRA Robot
Andy Bang writes: 
In build 2.1.0.1081.
[27 Jul 2009 22:14] Enterprise Tools JIRA Robot
Marcos Palacios writes: 
Verified fixed in advisor bundle 2.1.0.1081.

The Administration advisor's rule "InnoDB Redo Logs Not Sized Correctly" has been renamed as "InnoDB Transaction Logs Not Sized Correctly". The rule's Problem Description and Advice's references to this log have also been renamed appropriately.
[28 Jul 2009 10:56] Tony Bedford
An entry has been added to the 2.1.0 changelog:

The Advisor rule “InnoDB Redo Logs Not Sized Correctly” has been renamed to “InnoDB Transaction Logs Not Sized Correctly”. The rule's Problem Description and Advice text have also been updated accordingly.