Bug #45789 Upgrade from 6.3.x directly to 7.0.y ndbmtd does not warn
Submitted: 26 Jun 2009 14:33 Modified: 20 Aug 2009 6:09
Reporter: Oli Sennhauser Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: cluster upgrade ndbmtd 7.0.6
Triage: Triaged: D3 (Medium) / R6 (Needs Assessment) / E6 (Needs Assessment)

[26 Jun 2009 14:33] Oli Sennhauser
Description:
Upgrading from 6.3.x to 7.0.6 ndbmtd makes the cluster crash instead of a warning that this is not allowed.

How to repeat:
Upgrade 6.3.x directly to 7.0.x ndbmtd.

Suggested fix:
Jonas states:

>> You must first upgrade to single-threaded ndbd, before changing to multi-threaded ndbmtd.
>>
>> i.e upgrade cluster 6.3.20 -> 7.0.6 ndbd
>>     upgrade 7.0.6 ndbd -> 7.0.6 ndbmtd
>>
>> the fact that we don't return a informative error message is also a bug
>> that should be reported.
[29 Jun 2009 13:13] Jørgen Austvik
Jon: Please make sure that documentation states that this is not supported
[29 Jun 2009 13:57] Jon Stephens
Please don't assign bugs to me without changing the category to Docs. Thanks!
[29 Jun 2009 14:00] Jon Stephens
Took care of this Friday per Oli's email.
[29 Jun 2009 14:11] Oli Sennhauser
Hi guys,

The idea of this bug was NOT to fix the docu (what Jon already did "long" ago). The idea was: See initial description!

Oli
[30 Jun 2009 5:30] Jon Stephens
Please open a new *Server* bug and assign it to a *developer*.

This *Documentation* bug has been fixed and closed!

Thanks!