Innodb 死锁，看起来 tx 自己锁了

Question

我收到死锁错误，但不明白为什么。下面的报告显示，第二个事务（..453，回滚），已经在 "space id 545 page no 7185 n bits 192 index PRIMARY of table orders.order_items" 上锁定并且 正在等待获得锁定完全一样.

第一个，...455也想拿到同样的锁，不过可以等，没问题...

所以看起来事务 ..453 自己锁定了？？

------------------------
LATEST DETECTED DEADLOCK
------------------------
2017-04-13 10:55:21 7f434dd30700
*** (1) TRANSACTION:
TRANSACTION 108696455, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 1
LOCK WAIT 5 lock struct(s), heap size 1184, 4 row lock(s), undo log entries 2
MySQL thread id 652170, OS thread handle 0x7f434ca25700, query id 268182543 10.9.14.13 orders updating
delete from order_items where id=13828382 and version='2017-04-11 12:28:02'
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 545 page no 7185 n bits 192 index `PRIMARY` of table `orders`.`order_items` trx id 108696455 lock_mode X locks rec but not gap waiting
*** (2) TRANSACTION:
TRANSACTION 108696453, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 1
5 lock struct(s), heap size 1184, 7 row lock(s), undo log entries 5
MySQL thread id 652151, OS thread handle 0x7f434dd30700, query id 268182547 10.9.14.11 orders updating
delete from order_items where id=13828386 and version='2017-04-11 12:28:02'
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 545 page no 7185 n bits 192 index `PRIMARY` of table `orders`.`order_items` trx id 108696453 lock_mode X locks rec but not gap
*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 545 page no 7185 n bits 192 index `PRIMARY` of table `orders`.`order_items` trx id 108696453 lock_mode X locks rec but not gap waiting
*** WE ROLL BACK TRANSACTION (1)

编辑：Table 创建代码：

CREATE TABLE `order_items` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `order_id` bigint(20) DEFAULT NULL,
  `catalog_number` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `posex` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `sap_item_name` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `currency` varchar(3) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `status` varchar(20) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `price` decimal(19,2) DEFAULT NULL,
  `quantity` decimal(19,10) DEFAULT NULL,
  `parent_item_posex` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `deleted` bit(1) DEFAULT NULL,
  `version` datetime NOT NULL,
  `created_date` datetime NOT NULL,
  PRIMARY KEY (`id`),
  KEY `FKbioxgbv59vetrxe0ejfubep1w` (`order_id`),
  CONSTRAINT `FKbioxgbv59vetrxe0ejfubep1w` FOREIGN KEY (`order_id`) REFERENCES `orders` (`id`),
  CONSTRAINT `order_items_ibfk_1`          FOREIGN KEY (`order_id`) REFERENCES `orders` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=14564054 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

Answer 1

正如 Rick James 所猜测的那样，它看起来只是一把双重相同的钥匙。至少在删除其中一个约束后，table 不再出现问题。

Innodb 死锁，看起来 tx 自己锁了

Innodb deadlock, looks like tx locks itself

mysql

deadlock

innodb