mysql死锁日志,求分析
------------------------
LATEST DETECTED DEADLOCK
------------------------
130305 13:10:11
*** (1) TRANSACTION:
TRANSACTION 0 10931803, ACTIVE 1 sec, process no 29361, OS thread id 1193658688 fetching rows
mysql tables in use 1, locked 1
LOCK WAIT 13982 lock struct(s), heap size 1275888, 684479 row lock(s), undo log entries 11794
MySQL thread id 3330009, query id 283841506 10.204.176.60 kt9 Updating
update sys_log set flag = 2 where flag = 1
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931803 lock_mode X waiting
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** (2) TRANSACTION:
TRANSACTION 0 10931807, ACTIVE 0 sec, process no 29361, OS thread id 1153501504 inserting, thread declared inside InnoDB 500
mysql tables in use 1, locked 1
25 lock struct(s), heap size 3024, 50 row lock(s), undo log entries 307
MySQL thread id 3330013, query id 283841839 10.207.251.27 kt9 update
INSERT INTO sys_log(id,`level`,`scene`,`role_name`,`role_id`,`reason`,`ts`,`target_id`,`data`,`uid_new`,`num`,`action`,`s`,`uid`,`type`,ctime) VALUES ('44435420',47,'Scene\-100:4194','慕容紫衣','Role\-7791\-s11','','2013\-03\-05 13:10:01','Item\-0052','{\"amount\":1\,\"item_id\":\"Item\-0052\"}','C8C366CA292489AB82499A22DCFBFD65',1,'item.use',1362449853450417664,'User\-8409\-s11',1,1362460211)
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931807 lock_mode X locks rec but not gap
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931807 lock_mode X locks gap before rec insert intention waiting
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** WE ROLL BACK TRANSACTION (2)
LATEST DETECTED DEADLOCK
------------------------
130305 13:10:11
*** (1) TRANSACTION:
TRANSACTION 0 10931803, ACTIVE 1 sec, process no 29361, OS thread id 1193658688 fetching rows
mysql tables in use 1, locked 1
LOCK WAIT 13982 lock struct(s), heap size 1275888, 684479 row lock(s), undo log entries 11794
MySQL thread id 3330009, query id 283841506 10.204.176.60 kt9 Updating
update sys_log set flag = 2 where flag = 1
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931803 lock_mode X waiting
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** (2) TRANSACTION:
TRANSACTION 0 10931807, ACTIVE 0 sec, process no 29361, OS thread id 1153501504 inserting, thread declared inside InnoDB 500
mysql tables in use 1, locked 1
25 lock struct(s), heap size 3024, 50 row lock(s), undo log entries 307
MySQL thread id 3330013, query id 283841839 10.207.251.27 kt9 update
INSERT INTO sys_log(id,`level`,`scene`,`role_name`,`role_id`,`reason`,`ts`,`target_id`,`data`,`uid_new`,`num`,`action`,`s`,`uid`,`type`,ctime) VALUES ('44435420',47,'Scene\-100:4194','慕容紫衣','Role\-7791\-s11','','2013\-03\-05 13:10:01','Item\-0052','{\"amount\":1\,\"item_id\":\"Item\-0052\"}','C8C366CA292489AB82499A22DCFBFD65',1,'item.use',1362449853450417664,'User\-8409\-s11',1,1362460211)
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931807 lock_mode X locks rec but not gap
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 160 page no 363589 n bits 88 index `PRIMARY` of table `kt9`.`sys_log` trx id 0 10931807 lock_mode X locks gap before rec insert intention waiting
Record lock, heap no 16 PHYSICAL RECORD: n_fields 22; compact format; info bits 0
0: len 8; hex 8000000002a607de; asc ;; 1: len 6; hex 000000a6ce5f; asc _;; 2: len 7; hex 80000040091274; asc @ t;; 3: len 1; hex 81; asc ;; 4: len 30; hex 453338463235383342323636433430353241344638443332393338393542; asc E38F2583B266C4052A4F8D3293895B;...(truncated); 5: len 12; hex 557365722d3532302d733130; asc User-520-s10;; 6: SQL NULL; 7: len 12; hex 526f6c652d3437342d733130; asc Role-474-s10;; 8: len 9; hex e997bee4b880e6b19f; asc ;; 9: len 4; hex 51357e2a; asc Q5~*;; 10: len 11; hex 5363656e652d33323a3837; asc Scene-32:87;; 11: len 2; hex 8033; asc 3;; 12: len 10; hex 736b696c6c2e63617374; asc skill.cast;; 13: len 0; hex ; asc ;; 14: len 30; hex 7b226c6576656c223a31362c22736b696c6c5f6964223a22536b696c6c2d; asc {"level":16,"skill_id":"Skill-;...(truncated); 15: len 0; hex ; asc ;; 16: len 4; hex 80000000; asc ;; 17: len 8; hex 92e86dfc9fbd0b00; asc m ;; 18: len 1; hex 80; asc ;; 19: len 8; hex 8000000051357e33; asc Q5~3;; 20: len 8; hex 8000000000000000; asc ;; 21: len 2; hex 8000; asc ;;
*** WE ROLL BACK TRANSACTION (2)
...全文
相关推荐
MySQL Innodb表导致死锁日志情况分析与归纳
本文主要分析了在MySQL InnoDB引擎中出现死锁的情况,特别是涉及一个插入操作和一个删除操作并发执行时引发的死锁问题。通过对具体案例的描述和日志的解析,深入探讨了死锁的原因,以及如何通过查看In
大牛出手MySQL死锁深入分析
本文将以一个具体的死锁案例为背景,深入分析MySQL中的死锁机制,探讨死锁的成因,并提出预防策略,旨在帮助读者清晰理解死锁问题的背景、阅读死锁日志的方法、深入剖析死锁的原因以及总结死锁问题。
mysql死锁以及死锁日志分析1
在代码逻辑中检查潜在的死锁情况,并进行相应的调整或重试策略。总之,理解MySQL的死锁现象、其日志分析以及如何预防是保证数据库高效、稳定运行的关键。
一次mysql死锁的排查过程
**死锁分析**日志中的详细信息揭示了死锁的形成过程:- **事务1**:开始时,事务1试图获取`a`为2的记录的行级X锁(用于删除操作)。然而,由于事务2已经持有了该行的锁,事务1进入等待状态。
mysql死锁分析
### MySQL死锁分析#### 死锁问题背景在MySQL的使用过程中,死锁是一个较为常见的现象,尤其是在并发量较大的应用场景下。


