mysqldump inherently incompatible with NDB? - Kevin Burton - com.mysql.lists.cluster

4 messages in com.mysql.lists.clustermysqldump inherently incompatible wit...

From	Sent On	Attachments
Kevin Burton	01 Dec 2006 21:35
Anatoly Pidruchny	01 Dec 2006 21:44
Jason Brooke	01 Dec 2006 21:45
Mikael Ronström	04 Dec 2006 02:13

Subject:	mysqldump inherently incompatible with NDB?
From:	Kevin Burton (bur...@tailrank.com)
Date:	12/01/2006 09:35:08 PM
List:	com.mysql.lists.cluster

Here's a thought I had...

With large tables the default value of MaxNoOfConcurrentOperations isnt' sufficient. This means that ALTER TABLE FOO ENGINE=NDBCLUSTER will always fail.

Same issue with TransactionDeadlockDetectionTimeout ...

We weren't able to ALTER our tables without increasing TransactionDeadlockDetectionTimeout...

That said maybe the correct upgrade procedure would be to either increase these values temporarily OR do a mysqldump.

The problem is that mysqldump creates one large INSERT which is problematic as well. If it could split up the insert into 100 row batches that would be ideal.

Thoughts? Is there any ideal solution to this problem?

Kevin