Bug #16150 Cluster Rolling Upgrade
Submitted: 3 Jan 2006 11:24 Modified: 19 Apr 2006 13:00
Reporter: Hartmut Holzgraefe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:4.1 OS:Linux (linux)
Assigned to: Jon Stephens CPU Architecture:Any

[3 Jan 2006 11:24] Hartmut Holzgraefe 
Description:
There doesn't seem to be any real (step-by-step) documentation on how to perform a rolling restart/upgrade within a cluster setup or in which order the different node types need to be started on a cluster software update.

Information on which version is compatible to which is also missing although
critical as even minor releases may not be compatible to each other.

How to repeat:
.

Suggested fix:
.
[4 Jan 2006 17:56] Hartmut Holzgraefe 
version compatibilites according to the matrix found in
5.0/ndb/src/common/util/version.c

.        <--------------------------> <------------>
.  5.0   2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
.        ^                          -->
.        |  <->            -->
.  4.1   8  9 10 11 12 13 14 15 16 
.        <-->  <---------->   <->

<-> full compatibility
--> only upgrade compatibility
[19 Apr 2006 13:00] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

Added new Upgrade/Downgrade section to 4.1/5.0/5.1 Manual Cluster chapter, including subsections "Rolling Upgrade/Downgrade" and "Upgrade/Downgrade Compatibility".

Closed bug.