Bug #43815 New topology is not discovered after previous replication group is renamed
Submitted: 24 Mar 2009 0:47 Modified: 22 May 2009 8:47
Reporter: Bill Weber Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S2 (Serious)
Version:2.0.5.7153 OS:Any
Assigned to: Darren Oldag CPU Architecture:Any

[24 Mar 2009 0:47] Bill Weber 
Description:
When on a page that does not show the server tree...after a first replication group has been renamed, the second replication group does not get discovered.

How to repeat:
- install and start dashboard
- go to Replication tab
- start agents which are monitoring a replication topology
- after topology is shown on Replication tab, click link to rename group "Replication 1" to "Test"
- start agents that are monitoring a second replication topology while the dashboard is still on the Replication tab (or any page that does not show the server tree)
| notice that after waiting several minutes (more than 5), the second topology does not show on the Replication tab
[24 Mar 2009 19:17] Darren Oldag 
fix pushed to trunk(2.1)

revision-id: oldag@mysql.com-20090324185715-ednrwmwg02onszlq
parent: jsled@asynchronous.org-20090324160403-5c1g9qlm483ckdxd
committer: Darren L. Oldag <oldag@mysql.com>
branch nick: Trunk
timestamp: Tue 2009-03-24 13:57:15 -0500
message:
  http://bugs.mysql.com/bug.php?id=43815
  http://bugs.mysql.com/bug.php?id=43816
  
  on a group rename, some stale metadata was left in the
  name/id bookkeeping for replication groups.  removing
  the stale entry on a rename corrects these problems.
[24 Mar 2009 19:20] Darren Oldag 
fix pushed to 2.0 maintenance tree

revision-id: oldag@mysql.com-20090324191840-pabngp4ohxo8qgtd
parent: merlin@dl380-g5-a.mysql.com-20090324181839-1s0r0gedqr6ro5ah
committer: Darren L. Oldag <oldag@mysql.com>
branch nick: TwoDotZero
timestamp: Tue 2009-03-24 14:18:40 -0500
message:
  http://bugs.mysql.com/bug.php?id=43815
  http://bugs.mysql.com/bug.php?id=43816
    
  on a group rename, some stale metadata was left in the
  name/id bookkeeping for replication groups.  removing
  the stale entry on a rename corrects these problems.
[24 Mar 2009 21:32] Bill Weber 
verified fixed in build 2.0.6.7156
[25 Mar 2009 18:57] Keith Russell 
Patch installed in versions => 2.1.0.1019.
[25 Mar 2009 20:48] Bill Weber 
verified fixed in 2.1.0.1019
[22 May 2009 8:47] Tony Bedford 
An entry was added to both the 2.0.6 and 2.1.0 changelogs:

A new topology was not discovered after the previous replication group was renamed.