Bug #107982 | router hangs for big SQL | ||
---|---|---|---|
Submitted: | 26 Jul 2022 13:50 | Modified: | 31 Aug 2022 17:10 |
Reporter: | Cristi Coteț | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Router | Severity: | S3 (Non-critical) |
Version: | 8.0.29 - 8.0.30 | OS: | CentOS |
Assigned to: | CPU Architecture: | x86 |
[26 Jul 2022 13:50]
Cristi Coteț
[27 Jul 2022 5:30]
MySQL Verification Team
Hi, Thanks for your report. We are working on this issue already. kind regards
[29 Aug 2022 7:07]
Marta Vazquez Gonzalez
Hi team! We have the same problem using mysqldump with large tables. The records have databin fields that exceed 16M. The process remains running on the server until timeout without any previous error. Could you tell me when this problem will be solved? We just upgraded to 8.0.30 from version 8.0.26 and are considering downgrading. We also have additional problems with TLSv1 and TLSv1.1 connections. Thank you very much. Regards
[31 Aug 2022 16:28]
Edward Gilmore
Posted by developer: Added the following note to the MySQL Router 8.0.31 release notes: Under certain circumstances, processing SQL statements of 16MB or larger, MySQL Router could become unresponsive.
[31 Aug 2022 17:10]
Cristi Coteț
Hi, The expected resolution is for the problem to be fixed. And not only under certain circumstances but it always happens for SQL 's bigger than 16Mb. Thank you
[1 Sep 2022 7:32]
Edward Gilmore
Posted by developer: Updated release note by request: Processing SQL statements of 16MB or larger caused MySQL Router to become unresponsive.
[7 Sep 2022 5:51]
Marta Vazquez Gonzalez
Hi Team! To try to solve this problem, we have connected a router in 8.0.26 version with an innoDB Cluster on 8.0.30 version and it seems to solve the problem. We don't know if this will cause other problems, but we haven't detected them yet. Please, if you know of any known problem for making this type of mixed version, we appreciate your information. Regards