Re: unable to restore one big table of 25G with mk-parallel-restore

[Rick James]

mysql> SHOW GLOBAL VARIABLES LIKE '%timeout%';
+----------------------------+----------+
| Variable_name              | Value    |
+----------------------------+----------+
| connect_timeout            | 10       |
| deadlock_timeout_long      | 50000000 |
| deadlock_timeout_short     | 10000    |
| delayed_insert_timeout     | 300      |
| innodb_lock_wait_timeout   | 50       |  **
| innodb_rollback_on_timeout | OFF      |
| interactive_timeout        | 28800    |  **
| lock_wait_timeout          | 31536000 |
| net_read_timeout           | 30       |
| net_write_timeout          | 60       |
| slave_net_timeout          | 3600     |
| wait_timeout               | 28800    |  **
+----------------------------+----------+

If you are using InnoDB, then innodb_lock_wait_timeout may be important.
If the mk scripts acts as "interactive", then interactive_timeout may be imporant. (It is similar to wait_timeout.)