mysql 不同索引更新_MySQL 死锁套路:再来看一例走不同索引更新的例子

前面几篇文章介绍了利用调试MySQL源码的方式来调试锁相关的信息,这里利用这个工具来解决一个比较简单的问题,线上的表字段较多,这里简单成为了一个表

CREATE TABLE `t3` (

`id` int(11) NOT NULL AUTO_INCREMENT,

`a` varchar(5) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',

`b` varchar(5) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',

PRIMARY KEY (`id`),UNIQUE KEY `uk_a` (`a`), KEY `idx_b` (`b`)

)

复制代码

sql语句如下

t1

update t3 set b = '' where a = "1";

t2

update t3 set b = '' where b = "2";

复制代码

我们先用之前debug的方式来看一下,这里两条语句分别加了哪些锁

第一条语句(通过唯一索引去更新记录)

update t3 set b = '' where a = "1";

6f8e45f9c6273867564420f39becbe64.png

a2c683c0310d540134492d5c3f1f2e26.png

3f33a51e8cf26dfa31c8bea1a4bf5921.png

整理一下,加了3个X锁,顺序分别是

序号

索引

锁类型

1

uk_a

X

2

PRIMARY

X

3

idx_b

X

第二条语句

update t3 set b = '' where b = "2";

1ed30339205d651173e1c9aab4cffa2e.png

dbda493818bb048483f05c596e957286.png

6db42f94319d33fd9f0c1bdcfc958f8b.png

整理一下,加了3个X锁,顺序分别是

序号

索引

锁类型

1

idx_b

X

2

PRIMARY

X

3

idx_b

X

两条语句从加锁顺序看起来就已经有构成死锁的条件了

968a849581cd2c97ab389b14d9090b38.png

手动是比较难模拟的,写个代码去跑一下

马上就出现了

------------------------

LATEST DETECTED DEADLOCK

------------------------

181102 12:45:05

*** (1) TRANSACTION:

TRANSACTION 50AF, ACTIVE 0 sec starting index read

mysql tables in use 1, locked 1

LOCK WAIT 3 lock struct(s), heap size 376, 2 row lock(s)

MySQL thread id 34, OS thread handle 0x70000d842000, query id 549 localhost 127.0.0.1 root Searching rows for update

update t3 set b = '' where b = "2"

*** (1) WAITING FOR THIS LOCK TO BE GRANTED:

RECORD LOCKS space id 67 page no 3 n bits 72 index `PRIMARY` of table `d1`.`t3` trx id 50AF lock_mode X locks rec but not gap waiting

Record lock, heap no 2 PHYSICAL RECORD: n_fields 5; compact format; info bits 0

0: len 4; hex 80000001; asc ;;

1: len 6; hex 0000000050ae; asc P ;;

2: len 7; hex 03000001341003; asc 4 ;;

3: len 1; hex 31; asc 1;;

4: len 0; hex ; asc ;;

*** (2) TRANSACTION:

TRANSACTION 50AE, ACTIVE 0 sec updating or deleting

mysql tables in use 1, locked 1

4 lock struct(s), heap size 1248, 3 row lock(s), undo log entries 1

MySQL thread id 35, OS thread handle 0x70000d885000, query id 548 localhost 127.0.0.1 root Updating

update t3 set b = '' where a = "1"

*** (2) HOLDS THE LOCK(S):

RECORD LOCKS space id 67 page no 3 n bits 72 index `PRIMARY` of table `d1`.`t3` trx id 50AE lock_mode X locks rec but not gap

Record lock, heap no 2 PHYSICAL RECORD: n_fields 5; compact format; info bits 0

0: len 4; hex 80000001; asc ;;

1: len 6; hex 0000000050ae; asc P ;;

2: len 7; hex 03000001341003; asc 4 ;;

3: len 1; hex 31; asc 1;;

4: len 0; hex ; asc ;;

*** (2) WAITING FOR THIS LOCK TO BE GRANTED:

RECORD LOCKS space id 67 page no 5 n bits 72 index `idx_b` of table `d1`.`t3` trx id 50AE lock_mode X locks rec but not gap waiting

Record lock, heap no 2 PHYSICAL RECORD: n_fields 2; compact format; info bits 0

0: len 1; hex 32; asc 2;;

1: len 4; hex 80000001; asc ;;

*** WE ROLL BACK TRANSACTION (1)

复制代码

跟我们线上的死锁日志一模一样

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值