Bug #6967 FLUSH TABLES WITH READ LOCK can't be killed if in a certain stage
Submitted: 2 Dec 2004 22:10 Modified: 2 Dec 2004 22:10
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.22 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[2 Dec 2004 22:10] Guilhem Bichot 
Description:
When FLUSH TABLES WITH READ LOCK is its 3rd stage, make_global_read_lock_block_commit(), it can't be killed with KILL.
This is quite a minor inconvenience as this stage usually does not take long. The problem here is that because of some other bug (6732, fixed in 4.0.23), this make_global_read_lock_block_commit() was entering an infinite loop. Having it killable would at least helped the user break the loop and get his server usable again.
As this is minor it will be fixed in 5.0.3.

How to repeat:
not easy, as this 3rd stage is quite short on simple testcases.
[2 Dec 2004 22:10] Guilhem Bichot 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

MySQL 5.0 tree:
ChangeSet@1.1705.1.1, 2004-12-02 23:02:38+01:00, guilhem@mysql.com