Bug #49251 deadlock/crash with concurrent truncate table and index statistics calculation
Submitted: 1 Dec 2009 8:23 Modified: 26 Aug 2010 1:21
Reporter: Oli Sennhauser Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.0.91,5.1.50, 5.5, 5.6.1 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: crash, innodb, semaphore waits

File: Maximum allowed size is 50MB.

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:

[11 Aug 2010 5:40] Shane Bester
repeated a hangup in 5.0.80, and saved stack traces, etc.  there was FK keys created after starting the test.

Attachment: bug49251_5.0.80_hang_stack_traces.txt (text/plain), 25.00 KiB.

[12 Aug 2010 6:27] Shane Bester
repeated on 5.1.49 with innodb plugin 1.0.10

Attachment: bug49251_5.1.49.stack_traces.txt (text/plain), 29.86 KiB.

[20 Aug 2010 19:45] Shane Bester
compile and run against a mysqld started with --innodb-lock-wait-timeout=1.  give it some minutes or hours to hang or crash

Attachment: bug49251.c (text/plain), 10.38 KiB.