Public bug reported:
Release: Ubuntu 10.04 LTS
Package Version: 5.1.41-3ubuntu12.6
Stopping a MySQL server can take some time, especially on a busy
database. If mysqld gets killed while having open connections, then
after the next start you will likely have a lot of tables corrupted.
The new upstart mechanism for starting/stopping mysql unfortunately behaves as
follows on a "service mysql stop":
1. First it will send a TERM signal to mysqld which is perfectly fine as mysqld
will do the same as if you would issue a mysqladmin shutdown command
2. If after 5 seconds the process is still not terminated, a KILL signal will
be send. This is really a very big issue since on busy servers lots of myisam
tables will be corrupted afterwards
Expected behaviour:
Send the term signal and wait for a certain amount of time (at least 1 minute).
If still not stopped, then simply give an error about this to the user
** Affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
** Tags: upstart
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
