Comment 5 for bug 1882527

The mysql bug ticket (https://bugs.mysql.com/bug.php?id=91423) mentions

[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.

--

the latest ubuntu code (based on 8.0.22) contains following mentions of TimeoutSec

koen@hpubuntu:~/Dev/personal/ubuntu/mysql$ grep -rR TimeoutSec *
mysql-8.0-8.0.22/packaging/deb-in/mysql-packagesource-server.mysql.service.in:TimeoutSec=0
mysql-8.0-8.0.22/packaging/deb-in/mysql-packagesource-server.mysql@.service.in:TimeoutSec=0
mysql-8.0-8.0.22/scripts/systemd/mysqld@.service.in:TimeoutSec=0
mysql-8.0-8.0.22/scripts/systemd/mysqld.service.in:TimeoutSec=0
mysql-8.0-8.0.22/debian/mysql-server-8.0.mysql.service:TimeoutSec=600

--> it seems there's still 1 mention of 600 seconds in the Debian/ubuntu package

I can take on this issue but it might take a few weeks forme to complete - ETA mid Jan 2021 as I'm pretty new at ubuntu bugfixing/packaging and I'll have some questions for some more expert people

- correct patch description
- how to involve Debian upstream
- how to make patches for several releases (I'll start with hirsute)

if it's more urgent don't hesitate to assign someone else