Re: Mysql NDB cluster - Big import fail
>
> 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.
Already tried the two choices but no luck
> You can run a grep to see how many inserts are
> created: grep -c INSERT slabb.dump
8058
>
> As Jon suggested, another options is to first
> import data into InnoDB and then run alter table
> and set engine to NDB.
I haven't tried changing the engine after the engine, but I will
>
> Have a good day!
>
> Kind Regards,
> Ted
Thanks
Subject
Views
Written By
Posted
1951
May 31, 2022 05:40AM
617
June 01, 2022 01:22AM
590
June 02, 2022 12:47AM
708
June 02, 2022 07:58AM
569
June 02, 2022 03:58PM
589
June 03, 2022 06:06AM
583
June 03, 2022 09:32AM
623
June 01, 2022 03:13AM
Re: Mysql NDB cluster - Big import fail
604
June 02, 2022 12:52AM
719
June 02, 2022 04:56AM
600
June 08, 2022 12:29AM
626
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.