用sysbench進行插入測試怎么也會產(chǎn)生死鎖？

songpure520

具體代碼如下

1. LATEST DETECTED DEADLOCK
   
2. ------------------------
   
3. 100712 11:48:30
   
4. *** (1) TRANSACTION:
   
5. TRANSACTION 326C2, ACTIVE 0 sec, process no 12558, OS thread id 42664203 inserting
   
6. mysql tables in use 1, locked 1
   
7. LOCK WAIT 6 lock struct(s), heap size 1216, 5 row lock(s), undo log entries 1
   
8. MySQL thread id 2662, query id 3361062 localhost root update
   
9. INSERT INTO sbtest values(25177686,0,' ','aaaaaaaaaaffffffffffrrrrrrrrrreeeeeeeeeeyyyyyyyyyy')
   
10. *** (1) WAITING FOR THIS LOCK TO BE GRANTED:
    
11. RECORD LOCKS space id 0 page no 814916 n bits 152 index `PRIMARY` of table `test`.`sbtest` trx id
    
12. 326C2 lock_mode X locks gap before rec insert intention waiting
    
13. *** (2) TRANSACTION:
    
14. TRANSACTION 326AB, ACTIVE 0 sec, process no 12358, OS thread id 39387198 inserting, thread declare
    
15. d inside InnoDB 500
    
16. mysql tables in use 1, locked 1
    
17. 5 lock struct(s), heap size 1216, 4 row lock(s)
    
18. MySQL thread id 2462, query id 3361009 localhost root update
    
19. INSERT INTO sbtest values(25177668,0,' ','aaaaaaaaaaffffffffffrrrrrrrrrreeeeeeeeeeyyyyyyyyyy')
    
20. *** (2) HOLDS THE LOCK(S):
    
21. RECORD LOCKS space id 0 page no 814916 n bits 152 index `PRIMARY` of table `test`.`sbtest` trx id
    
22. 326AB lock_mode X locks gap before rec
    
23. *** (2) WAITING FOR THIS LOCK TO BE GRANTED:
    
24. RECORD LOCKS space id 0 page no 814916 n bits 152 index `PRIMARY` of table `test`.`sbtest` trx id
    
25. 326AB lock_mode X locks gap before rec insert intention waiting
    
26. *** WE ROLL BACK TRANSACTION (2)
    

復(fù)制代碼

為什么會產(chǎn)生這種情況！像這種單表并行插入應(yīng)該效率很快��！怎么也會產(chǎn)生死鎖?

surpass_li

不懂,幫頂