Bug #102097 | Cloning fails with low wait_timeout | ||
---|---|---|---|
Submitted: | 31 Dec 2020 8:51 | Modified: | 25 Jan 2021 20:04 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Clone Plugin | Severity: | S3 (Non-critical) |
Version: | 8.0.21, 8.0.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[31 Dec 2020 8:51]
Daniël van Eeden
[4 Jan 2021 13:38]
MySQL Verification Team
Hello Daniël, Thank you for the report and feedback. Verified as described on 8.0.22 build. regards, Umesh
[25 Jan 2021 20:04]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.24 release, and here's the proposed changelog entry from the documentation team: A long running remote cloning operation failed due to a low wait_timeout setting on the donor MySQL Server instance. Donor threads use the MySQL Server wait_timeout setting when listening for Clone protocol commands. To avoid timeout failures on donor instances with a low wait_timeout setting, the Clone idle timeout is now set to the default wait_timeout setting, which is 28800 seconds (8 hours). Clone network read and write timeout values were also increased. Thank you for the bug report.