MySQL Bugs: #18210: ndb_restore fails of 5.0 backup that is restored on 5.1

Bug #18210	ndb_restore fails of 5.0 backup that is restored on 5.1
Submitted:	14 Mar 2006 8:04	Modified:	23 Apr 2006 1:04
Reporter:	Johan Andersson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Linux (Linux)
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
I have been trying to move my test database from 5.0 to 5.1.  Having started the cluster (using --initial on the ndbd nodes) I am unable to restore a backup of the database.  I get the following output:

$ /usr/local/mysql/bin/ndb_restore -m -r -n 6 -b 1
Nodeid = 6
Backup Id = 1
backup path = ./
Ndb version in backup files: Version 5.0.15
Configuration error: Illegal reply from server : 
Failed to initialize consumers

NDBT_ProgramExit: 1 - Failed

How to repeat:
.

Suggested fix:
-

The backup is taken from a 5.0 single node cluster

i didn't succeed either, getting a slightly different message though (using debug builds):

Nodeid = 2
Backup Id = 1
backup path = ./
Ndb version in backup files: Version 5.0.20
ndb_restore: NdbDictionaryImpl.cpp:2048: static int NdbDictInterface::parseTableInfo(NdbTableImpl**, const Uint32*, Uint32, bool): Assertion `impl->m_fragmentCount > 0' failed.

This is just a DBUG_ASSERT and should not appear in a proper release.
Works fine without it.
Workaround, re-compile without debug.

pushed to 5.1.10

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.10 changelog. Closed.