Bug #24020 NDB: rolling upgrade of 5.1.11 to 5.1.12 failing
Submitted: 6 Nov 2006 16:11 Modified: 6 Nov 2006 18:58
Reporter: Kris Buytaert (Candidate Quality Contributor) Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.12 OS:
Assigned to: Jonas Oreland CPU Architecture:Any
Tags: upgrade rolling ndbd

[6 Nov 2006 16:11] Kris Buytaert
Initial state : working cluster on 5.1.11 ,  
started upgrading the ndb_mgmd nodes ,  worked.

Shutted down the passive node in the cluster.  Upgraded both ndbd and mysql etc from 5.1.11 to 5.1.12

Upon trying to start ndbd on the upgraded node again it fails with 

Time: Monday 6 November 2006 - 16:48:52
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: dblqh/DblqhMain.cpp
Error object: DBLQH (Line: 13877) 0x0000000a
Program: ndbd
Pid: 7219

How to repeat:
try to restart ndbd after upgrading the node from 5.1.11 to 5.1.12

Suggested fix:
Not sure if it is actually supposed to work :)
[6 Nov 2006 16:12] Kris Buytaert
ndb error and tracefiles

Attachment: 24020.tar.gz (application/x-gzip, text), 129.09 KiB.

[6 Nov 2006 17:07] Jonas Oreland

we dont support rolling upgrades until 5.1 has become GA
[6 Nov 2006 18:58] Kris Buytaert
Just for my planning, would a rolling upgrade from 4.1.12 to 5.1.something work then ?
[7 Nov 2006 9:33] Jonas Oreland
no, sorry :-(

we currently dont support online upgrade between 4.1, 5.0 & 5.1

however, starting from 5.1 we plan to always be online upgradable...