Bug #49086 typo in advisor Slave Has Problem Communicating With Master (v 1.3 *)
Submitted: 25 Nov 2009 6:59 Modified: 11 Dec 2009 15:06
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:2.1.0.1096 OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[25 Nov 2009 6:59] Shane Bester
Description:
description contains a typo:

Slaves must connect to a master to get the latest data from the master. If they cannot connect, or periodically have trouble connecting, replication may fall behind (i.e. the slave may not have the lastest data that was written to the master).

How to repeat:
s/lastest/latest/
[25 Nov 2009 9:56] Sveta Smirnova
Thank you for the report.

Verified as described.
[3 Dec 2009 23:31] Enterprise Tools JIRA Robot
Andy Bang writes: 
Pushed up to revision 303.
[7 Dec 2009 22:26] Enterprise Tools JIRA Robot
Marcos Palacios writes: 
Verified fixed in advisor bundle 2.2.0.1571.
[11 Dec 2009 15:06] MC Brown
No documentation needed