4 messages in com.mysql.lists.clusterRe: mysqldump inherently incompatible...
FromSent OnAttachments
Kevin Burton01 Dec 2006 21:35 
Anatoly Pidruchny01 Dec 2006 21:44 
Jason Brooke01 Dec 2006 21:45 
Mikael Ronström04 Dec 2006 02:13 
Subject:Re: mysqldump inherently incompatible with NDB?
From:Jason Brooke (jas@mammoth.com.au)
Date:12/01/2006 09:45:49 PM
List:com.mysql.lists.cluster

G'day Kevin

Not sure about how to change the behaviour of alter table, but you can try disabling extended inserts with mysqldump:

-O extended-insert=0

I've done this in order to avoid increasing MaxNoOfConcurrentOperations and it works. Data imports are slower as a result though, as expected.

Jason

Kevin Burton wrote:

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