Bug #101285 Cannot restore dumped data via mysql router
Submitted: 23 Oct 2020 11:11 Modified: 30 Dec 2020 4:26
Reporter: Toshinori SUGITA Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Router Severity:S2 (Serious)
Version:8.0.22 OS:Ubuntu (20.04)
Assigned to: MySQL Verification Team CPU Architecture:Any

[23 Oct 2020 11:11] Toshinori SUGITA
Description:
I cannot restore data made from mysqldump without --skip-extended-insert option.

How to repeat:
1. dump recored data from mysqldump without --skip-extended-insert option.
2. restore that via mysql router 8.0.22 with unix domain socket.
3. stalled and timeout.

the dump data has very long INSERT SQL about 1MB.
I picked up only one line from the dump data.
I try to insert the picked data repeatly with shrink the line.

1MB line - NG.
512KB line - NG.
220KB line - NG.
110KB line - OK.

otherwize, when dump data made from mysqldump with --skip-extended-insert option,
I can restore fine.
[27 Oct 2020 22:13] MySQL Verification Team
Hi,

When executing mysqldump you need to tell mysqldump to not generate "extended inserts" in blocks larger then max_allowed_packet set on the server you are going to import this dump on.

https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_allowed_pa...

https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html#option_mysqldump_max-allowed-packet

all best
Bogdan
[29 Oct 2020 9:30] Toshinori SUGITA
Hi, Bogdan.
Thank you for your reply.

But, My probrem dosn't resolved.
I missed to report at first time.

1. server's "max_allowed_packet" parameter has been set to 32MB.
2. router's "net_buffer_length" parameter has been set to 1MB, too.
3. In the same situation using version 8.0.21 (router and server, ubuntu 20.04 deb package), I was not gotten this probrem.
4. Dump data that made by mysqldump was from mysql server 5.6.21 with default parameters. It dumped about 1MB each insert lines.
[30 Dec 2020 4:26] MySQL Verification Team
Hi,

Yes, we have a bug in router 8.0.22 where big packages do not work trough. Should be fixed when 8.0.23 is out.

Thanks
Bogdan
[30 Dec 2020 4:28] MySQL Verification Team
duplicate of https://bugs.mysql.com/bug.php?id=101406

Bogdan