Bug #98203 mysql dump "sufficiently long" network timeout too short
Submitted: 13 Jan 2020 14:09 Modified: 15 Jan 2020 3:04
Reporter: Georgi Kodinov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[13 Jan 2020 14:09] Georgi Kodinov 
Description:
Hard coded 700 seconds mysqldump network-timeout
8.0 mysqldump has a boolean option --network-timeout to set 700 seconds network timeouts. This is hard coded https://github.com/mysql/mysql-server/blob/8.0/client/mysqldump.cc#L1518
700 seconds is large enough in most cases, but why is it a boolean, not an integer argument?

How to repeat:
Run mysqldump against an unresponsive server

Suggested fix:
It would be better if we can set reasonably large, but not infinite timeout (e.g. 86400 — 1 day).
[15 Jan 2020 3:04] Paul DuBois 
Posted by developer:
 
Fixed in 8.0.20.

The mysqldump internal network timeout was increased from 700 to
86400 seconds to accommodate connecting to busy or unresponsive
servers.