Re: Mysql NDB cluster - Big import fail
Hello Cesar,
Sorry to hear you are having problems importing your dumpfile.
mysqldump uses large extended inserts by default, this is most likely the problems you are facing. This works for InnoDB but NDB is not that good with large transactions.
You can work around this by creating a new dumpfile. You have 2 options, either remove extended inserts completely:
mysqldump --extended-insert=0
Or you can set "net_buffer_length" to control the size of the extended inserts:
mysqldump --net_buffer_length=4096
I would try to set net_buffer_length=4096 and re-run the import.
You can run a grep to see how many inserts are created: grep -c INSERT slabb.dump
As Jon suggested, another options is to first import data into InnoDB and then run alter table and set engine to NDB.
Have a good day!
Kind Regards,
Ted
Subject
Views
Written By
Posted
1358
May 31, 2022 05:40AM
435
June 01, 2022 01:22AM
414
June 02, 2022 12:47AM
522
June 02, 2022 07:58AM
416
June 02, 2022 03:58PM
406
June 03, 2022 06:06AM
412
June 03, 2022 09:32AM
Re: Mysql NDB cluster - Big import fail
442
June 01, 2022 03:13AM
433
June 02, 2022 12:52AM
526
June 02, 2022 04:56AM
419
June 08, 2022 12:29AM
471
June 02, 2022 09:49AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.