Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5.29-galera
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Resolving of multi-master conflicts can lead to situation when innodb kernel-mutex is tried to be locked twice by same THD:
130215 13:31:45 [Note] WSREP: BF kill (1, seqno: 1148093), victim: (1906) trx: 235097905
130215 13:31:45 [Note] WSREP: Aborting query: DELETE FROM comm01 WHERE p >= 1000
130215 13:31:45 [Note] WSREP: kill trx QUERY_EXEC for 235097905
130215 13:31:45 [Note] WSREP: kill query for: 1906
130215 13:31:45 InnoDB: Assertion failure in thread 140646447503104 in file sync0sync.ic line 207
InnoDB: Failing assertion: !mutex_own(mutex)
How to reproduce:
start two nodes and issue conflicting SQL load on both nodes
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Fix pushed in revision: http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3380
Adapting to THD::awake() changes in MariaDB
The problem is due to changes in THD::awake(), which now calls new handler method ha_kill_query()
InnoDB implementation of kill query (innobase_kill_query), enters kernel mutex.