Bug #56813 Slave re-synchronization should be seamless to the dashboard

Submitted:	16 Sep 2010 8:42	Modified:	16 Sep 2010 8:49
Reporter:	Roger David Nay	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S3 (Non-critical)
Version:	All	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Keeping the host uuid in the mysql.inventory is problem, especially when re-synchronizing slaves from the master, or any sort of reinstallation. Special handling (workarounds) are required to not lose and put back information to retain the same dashboard location and history.

How to repeat:
Install a slave with agent monitoring and then re-synchronize the slave from the master.

Suggested fix:
Make slave re-synchronization or re-installation seamless to the dashboard. Keep configuration details local to the agent (as well as in the mysql.inventory?). 

Maybe some way of signaling in the dashboard, this new server, is the same as this other old server, please combine them would achieve the same thing (still manual intervention required, but better).

This is a duplicate of Bug#52403.

Now, its not a duplication. As i mentions within the other bug, this one describe the change of hostid/uuid without any change at the configuration. The other bug describes only the loss of historical data in case of such an change.

This Bug is on the agent side. The other one on the (MEM)Server side.

Page generated in 0.040 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.