Comment 0 for bug 1882527
Revision history for this message
| Warwick Bruce Chapman (warwickchapman) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
MySQL on 20.04 has TimeoutSec set to 600 (IIRC) in the systemd script. This has the effect of killing the MySQL process if this timeout is reached.
IMHO this is a Very Bad Idea. A database server process should only be force killed by a user action.
I would prefer that the server had unlimited time to cleanly shutdown and startup (eg if recovering).
Our DB is about 500GB with some very large tables (for us at least) eg. 250GB and we've had more than a few unfortunate delays as a result of delayed startup caused by recoveries because MySQL was killed prematurely.
Because MySQL 8.0 has reduced the default logging level, it was not clear to me that the process was being force killed.
I believe the MySQL team are of the same view as me per https:/
```
[12 Jul 2019 15:57] Paul Dubois
Posted by developer:
Fixed in 8.0.18.
On Debian, long InnoDB recovery times at startup could cause systemd
service startup failure. The default systemd service timeout is now
disabled (consistent with RHEL) to prevent this from happening.
```