Bug #57251 assert in sync_thread_add_level() for TRUNCATE
Submitted: 5 Oct 2010 15:02 Modified: 12 Oct 2010 14:58
Reporter: Mikhail Izioumtchenko Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.5 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[5 Oct 2010 15:02] Mikhail Izioumtchenko
Description:
a crash like below observed a few times recently in my stress tests:

101004 13:10:47  InnoDB: Assertion failure in thread 1247856960 in file ...storage/innobase/sync/sync0sync.c line 1193
101004 13:10:47 - mysqld got signal 6 ;

in TRUNCATE

How to repeat:
reproducibility is rather low
[6 Oct 2010 14:26] Davi Arnaut
I get this same backtrace with the following test case:

--source include/have_innodb.inc

CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=INNODB;
CREATE TABLE t2 (fk INT NOT NULL, FOREIGN KEY (fk) REFERENCES t1 (pk)) ENGINE=INNODB;
TRUNCATE TABLE t2;
DROP TABLE t2;
DROP TABLE t1;

Testing on a vanilla mysql-5.5-bugteam tree.
[11 Oct 2010 18:00] Davi Arnaut
Could this be a duplicate of Bug#57248? Test case does not hit the assertion in latest 5.5-bugteam.
[12 Oct 2010 14:59] Mikhail Izioumtchenko
does look like a duplicate of Bug#57248 given that the testcase
won't fail with r3176, mysql-5.5-innodb yet it does fail
when the fix for Bug#57248 is reverted