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
[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.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 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.