MySQL Bugs: #37346: innodb does not detect deadlock between update and alter table

Bug #37346	innodb does not detect deadlock between update and alter table
Submitted:	11 Jun 2008 14:35	Modified:	7 Mar 2010 18:34
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Locking	Severity:	S3 (Non-critical)
Version:	5.0,5.1	OS:	Any
Assigned to:	Dmitry Lenev	CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

output of lock monitor, processlist, original testcase output showing 0 tps

Attachment: bug37346_innodb_lock_monitor.txt (text/plain), 12.71 KiB.

testcase. run against mysqld with long innodb_lock_wait_timeout until queries hang

Attachment: bug37346.c (text/plain), 6.70 KiB.

thread stacks of 2x update and 1x alter table

Attachment: bug37346_thread_stacks_during_hang.txt (text/plain), 6.83 KiB.