Really slow shutdown with Innodb, db not accessible?

[Nick Arnett]

For the last four hours or so, I've been waiting for MySQL (4.0.12 on W2K)
to complete a shutdown. The fast shutdown flag is not set
(innodb_fast_sh utdown=0), so I assume it is doing a purge and merge... but
in the meantime, I don't have any access to the server -- clients simply
can't connect. This is a real problem, since it renders the database
useless for a long period of time. My Innodb table is about 15 GB and
probably has about 10 million records in various tables.

When the darn thing finally shuts down, I'll restart with fast shutdown on,
but I'm wondering how foolish it would be to kill the process, given that
Innodb should then do a crash repair. Would the crash repair take longer
than what it's doing now? Would the server be inaccessible as it is now?

Besides enabling fast shutdown, what else will help avoid this kind of thing
in the future?

Thanks for any info...

--
Nick Arnett
Phone/fax: [phone]
na*****@senti-metrics.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw