Bug #51958 Upgrading MySQL Enterprise Monitor documentation - just stop everything
Submitted: 11 Mar 2010 16:23 Modified: 15 Mar 2010 15:15
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: MC Brown CPU Architecture:Any

[11 Mar 2010 16:23] Roger David Nay
Reword this:

"Before updating the MySQL Enterprise Service Manager stop all agents that are reporting to that MySQL Enterprise Service Manager. If you are updating the MySQL Enterprise Monitor Agent you must also stop the MySQL Enterprise Service Manager."


How to repeat:

Suggested fix:
"If you want to upgrade any element of the MEM setup, you need to first shut down all of the agents and the monitor server".

- or - 

"You need to shut down all of the agents and the monitor server to perform any upgrade."

I doubt it is a good idea to only update one agent to a different version, which appears to be the only situation not covered from the above change.
[15 Mar 2010 15:15] MC Brown
I've updated the documentation according to advice from the MEM team.

For major upgrades (1.3->2.0) you should down everything and upgrade. 

For minor updates where compatibility exists, you can upgrade individual agents and components without taking down the entire monitoring environment. There should be no reason to take everything down for a minor upgrade.