莫名其妙的 InnoDB 死锁答案

【问题标题】：Baffling InnoDB deadlock莫名其妙的 InnoDB 死锁
【发布时间】：2013-04-22 07:18:07
【问题描述】：

这个 InnoDB 僵局真的让我抓狂。据我所知：

事务 (1) 正在等待“应用程序”上的 PRIMARY
后者已被 (2) 用于一些运行时间较长的更新（SELECT * FROM applications WHERE ID = xxxx FOR UPDATE）

到目前为止，一切都很好 - 人们会期望 (1) 等待锁定，然后继续其工作。

但是，一旦 (2) 准备好保存它的工作（并提交事务），它就会因某种原因而失败并出现死锁，因为 (1) 已设法锁定某个二级索引。 如果 PRIMARY 由 (2) 持有，那么 (1) 到底是如何设法获得行上的任何锁的。

如果 (2) 最初获得了 PRIMARY 锁（SELECT * FROM applications WHERE ID = xxxx FOR UPDATE），那么它也会在所有二级索引上设置锁。如果tasked==NULL，它是否可能不会锁定“tasked”索引，从而允许（1）在获得PRIMARY锁定之前获得“tasked”锁定？

我没有运气复制这个场景..

谢谢！

劳里

------------------------
LATEST DETECTED DEADLOCK
------------------------
130428 17:04:06
*** (1) TRANSACTION:
TRANSACTION A369A8C, ACTIVE 1 sec fetching rows
mysql tables in use 3, locked 3
LOCK WAIT 217 lock struct(s), heap size 31160, 636 row lock(s)
MySQL thread id 13310554, OS thread handle 0x7f06cc2d7700, query id 177699568 217.146.78.151 shard67 Sending data
SELECT `applications`.* FROM `applications`
 LEFT JOIN `applicants` ON applicants.ID = applications.applicant_ID
 LEFT JOIN `regions` ON regions.ID = applicants.region_ID WHERE (status <> 'Blank') AND (status <> 'Closed') AND (revised < 1367154245) AND (tasked IS NULL OR tasked < 1367147045) AND (commence_year >= '2013') AND (regions.instance_ID = '1') ORDER BY `tasked` ASC, `ID` ASC LIMIT 20 FOR UPDATE
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 20021 page no 1192 n bits 80 index `PRIMARY` of table `dream-shard67`.`applications` trx id A369A8C lock_mode X locks rec but not gap waiting
*** (2) TRANSACTION:
TRANSACTION A369A87, ACTIVE 1 sec updating or deleting
mysql tables in use 1, locked 1
16 lock struct(s), heap size 3112, 22 row lock(s), undo log entries 5
MySQL thread id 13310563, OS thread handle 0x7f06cc151700, query id 177699599 217.146.76.127 shard67
UPDATE `applications` SET `revised` = '1367157846', `tasked` = '1367157846', `revision_ID` = '140649', `xml` = 'Zms6\noMmI$%[v....snipped binary data
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 20021 page no 1192 n bits 72 index `PRIMARY` of table `dream-shard67`.`applications` trx id A369A87 lock_mode X locks rec but not gap
*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 20021 page no 292 n bits 1280 index `tasked` of table `dream-shard67`.`applications` trx id A369A87 lock_mode X locks rec but not gap waiting
*** WE ROLL BACK TRANSACTION (2)

【问题讨论】：

标签： mysql innodb deadlock database-deadlocks

【解决方案1】：

确保您完成以下大部分操作：
http://dev.mysql.com/doc/refman/5.0/en/innodb-deadlocks.html

【讨论】：