Bug #27281 Warning at 'failed wait_for_lock'
Submitted: 20 Mar 2007 8:19 Modified: 11 Apr 2008 17:33
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Locking Severity:S3 (Non-critical)
Version:5.0 OS:Windows (windows)
Assigned to: CPU Architecture:Any
Tags: read locks, wait_for_lock, write locks

[20 Mar 2007 8:19] Shane Bester 
Description:
During shutdown of the mysqld database, we see this with running the debug binary:

Version: '5.0.27-community-debug'  socket: ''  port: 3306  MySQL Community Edition - Debug (GPL)
070225 22:12:50 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-debug: Normal shutdown

Warning at 'failed wait_for_lock': No write locks and waiting read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': No write locks and waiting read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': No write locks and waiting read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': Write lock 7 waiting while no exclusive read locks
Warning at 'failed wait_for_lock': No write locks and waiting read locks

How to repeat:
no idea yet.  not sure if this warning is harmless or not.  at least this bug report might give some further information to users in case they receive such errors in future.

Suggested fix:
.
[25 Jul 2007 13:43] Sveta Smirnova 
Thank you for the report.

How do you stop the server?
[1 Mar 2008 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[11 Apr 2008 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".