MySQL Bugs: #46632: Deleting a server from the UI takes several minutes

Bug #46632	Deleting a server from the UI takes several minutes
Submitted:	10 Aug 2009 15:15	Modified:	21 Aug 2009 9:35
Reporter:	Diego Medina	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.1.0.1085	OS:	Any
Assigned to:	Mark Matthews	CPU Architecture:	Any

Description:
On a large deployment, deleting a mysql instance from the UI takes several minutes to complete (To finish loading the Manager servers page)

Note: This is a setup where I have 305 mysql instances, data for about 5 months and 203 agents reporting information.

How to repeat:
1- Monitor a large number of servers (203)
2- After collecting data for several weeks, delete one server
3- Notice how long that takes

Mark Matthews writes: 
This fix does not speed up the delete process (which runs on a background thread, and has for quite some time), but instead ensures that Hibernate's L2 caches don't get entirely flushed due to a bulk delete, which is what made the other pages in the application load slowly after the delete. The application was essentially in the "cold start" scenario after the deletion of the server, which is why pages loaded slowly after the deletion of a server.

Diego Medina writes: 
Present on 2.1.0.1094

Diego Medina writes: 
Verified fixed on 2.1.0.1094

Deleting a server (same conditions as before) takes only 20-30 seconds (it used to take about 6-9 minutes)

A note has been added to the 2.1 changelog: 

When deleting a server within MySQL Enterprise Dashboard where there was a lot of historical data and/or a large number of instances being monitored, the deletion process could take some time and affect the loading of all pages within MySQL Enterprise Dashboard The process should no longer affect the performance UI.