Bug #38675 changing master/slave roles does not reflect properly in MEM
Submitted: 8 Aug 2008 16:42 Modified: 3 Oct 2008 16:40
Reporter: Sloan Childers Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:1.3.2, 1.3.3, 2.0.5 OS:Any
Assigned to: Sloan Childers CPU Architecture:Any

[8 Aug 2008 16:42] Sloan Childers
Description:
Switching master/slave roles on servers and the change does not get reflected properly in MEM.  They are just sort of "stuck."

How to repeat:
Promote a previously discovered slave or demote a previously discovered master, wait 5 minutes for discovery to run again and see that the UI does not properly sort this out.

Suggested fix:
Fix the replication discovery algorithm to handle changing roles.
[3 Oct 2008 16:40] Sloan Childers
Between development/test/support we can't reproduce the problem in house and the customer has now told us that it is not that big a deal after all.
[31 Mar 2009 6:50] MySQL Verification Team
MySQL 5.1, MEM 2.0.5.7513

A customer reported they have a a single master, multiple save replication set up.

They removed the master and promoted one of the slaves to be the new master,
but it was displayed in MEM as a "master/slave", instead of just "master".