Bug #43671 InnoDB hang on rseg->mutex in trx0trx.c:1846 and trx0roll.c:934
Submitted: 16 Mar 2009 9:56 Modified: 24 Jan 2010 16:44
Reporter: Axel Schwenke Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.0.56sp1 OS:Linux (x86_64)
Assigned to: CPU Architecture:Any
Tags: Semaphore

[16 Mar 2009 9:56] Axel Schwenke 
Description:
InnoDB crashes the server after a long semaphore wait. The mutex is rseg->mutex. There are 3 treads waiting:

1x COMMIT at trx0trx.c line 1846
2x ROLLBACK at trx0roll.c line 934

There are several other active transactions, both select and insert.

Might be related to bug #29560, bug #19081, bug #20358.

How to repeat:
Not repeated. Its the first report for InnoDB hanging on this mutex. Reporting this as bug anyway, maybe somebody else gets the same.
[17 Mar 2009 9:09] Sveta Smirnova 
From error log:

InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
090313  7:51:08InnoDB: Assertion failure in thread 1147169120 in file srv0srv.c line 2095
[31 Mar 2009 13:49] MySQL Verification Team 
Bug: http://bugs.mysql.com/bug.php?id=34459 has similar error log output.
[24 Dec 2009 16:44] Valeriy Kravchuk 
Bug #48192 also looks related. Do you have innodb_file_per_table set?
[25 Jan 2010 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".