Bug #41519 master-uuid is not used for replication topology discovery
Submitted: 16 Dec 2008 21:12 Modified: 4 Mar 2009 11:27
Reporter: Mark Leith
Status: Closed
Category:Monitoring: Server Severity:S3 (Non-critical)
Version:2.0.7015 OS:Any
Assigned to: MC Brown Target Version:

[16 Dec 2008 21:12] Mark Leith 
Description:
The agent now collects master-uuid by reading the master.info file, and then running a
select directly against it's master to try and read the mysql.inventory table on the
master for the instance uuid. 

However, this is not being used correctly within the replication topology discovery
within the server. 

How to repeat:
o Set up master/slave by using a virtual IP to connect the master from the slave
o Make sure the replication user on the master has privileges for mysql.inventory
o Set up agents for each
o Start the agent on the slave as root
o Check the replication topology

Suggested fix:
Use master-uuid within the topology discovery process as well.
[26 Feb 2009 1:05] Keith Russell 
Patch installed in versions => 2.0.5.7146.
[3 Mar 2009 21:37] Diego Medina 
Verified fixed on 2.0.5.7148
[4 Mar 2009 11:27] Tony Bedford 
An entry was added to the 2.0.5 changelog:

The master_uuid was not used for replication topology discovery.

The agent collected master_uuid by reading the master.info file, and then running a
SELECT directly against its master. This was to try and read the mysql.inventory table on
the master to obtain the instance master_uuid.

However, this was not being used correctly by the replication topology discovery within
the server.