Bug #43816 Replication group is renamed back to default after new topology discovered

Submitted:	24 Mar 2009 0:57	Modified:	22 May 2009 9:00
Reporter:	Bill Weber	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.0.5.7153	OS:	Any
Assigned to:	Darren Oldag	CPU Architecture:	Any

Description:
When on a page that does show the server tree...a replication group that was changed is renamed back to a default name when a new replication topology is 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"
- go to the Monitor tab (or any page that shows the server tree) and start agents that are monitoring a second replication topology
| notice that after the 2nd replication group is discovered as "Replication 1", the first group now shows (eventually) as "Replication 2" instead of "Test"

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.

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.

verified fixed in build 2.0.6.7156

Patch installed in versions => 2.1.0.1019.

verified fixed in 2.1.0.1019

An entry was added to the 2.1.0 changelog:

The Replication Group was renamed back to its default name after a new topology was discovered.

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.