On Aug 24, 2010, at 1:22 PM, Johan Kiviniemi wrote: >> Would there be an indication anywhere for users that they're waiting > on mysql to die? > > The ‘stop’ command having not returned yet, and ‘status jobname’ saying > ‘stopping’. > > If a bug in a service causes a stop request not to stop it, the service > should be fixed. >
I had made some assumptions about the shutdown process until now based on my past experience, but it is detailed here: http://dev.mysql.com/doc/refman/5.1/en/server-shutdown.html So the only thing that *should* cause a really long shutdown time is a giant transaction rollback. > As for the pseudocode, I don’t think respawning is expected behavior > when the user has requested a job to stop. Agreed... I'm still worried about restarts during upgrades spinning forever though. I guess as long as the script tells the user "Waiting for mysql to shutdown.. ## threads still running.." every 30 seconds that would probably be enough. -- 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
