mysql 奇怪的死锁问题求解

2016-06-13 10:04:27 +08:00
 sujin190
InnoDB: Warning: a long semaphore wait:
--Thread 139666312808192 has waited at buf0buf.cc line 2576 for 342.00 seconds the semaphore:
S-lock on RW-latch at 0x7f077d5e08c0 created in file buf0buf.cc line 1069
number of readers 0, waiters flag 0, lock_word: 100000
Last time read locked in file btr0cur.cc line 3592
Last time write locked in file /export/home/pb2/build/sb_0-17604105-1452827438.0/rpm/BUILD/mysql-5.6.29/mysql-5.6.29/storage/innobase/buf/buf0buf.cc line 3691
InnoDB: Warning: a long semaphore wait:
--Thread 139665275766528 has waited at buf0buf.cc line 2576 for 331.00 seconds the semaphore:
S-lock on RW-latch at 0x7f077d5e08c0 created in file buf0buf.cc line 1069
number of readers 0, waiters flag 0, lock_word: 100000
Last time read locked in file btr0cur.cc line 3592
Last time write locked in file /export/home/pb2/build/sb_0-17604105-1452827438.0/rpm/BUILD/mysql-5.6.29/mysql-5.6.29/storage/innobase/buf/buf0buf.cc line 3691
InnoDB: Warning: a long semaphore wait:
--Thread 139661653473024 has waited at buf0buf.cc line 2576 for 313.00 seconds the semaphore:
S-lock on RW-latch at 0x7f0701de88c0 created in file buf0buf.cc line 1069
number of readers 0, waiters flag 0, lock_word: 100000
Last time read locked in file row0sel.cc line 3220
Last time write locked in file /export/home/pb2/build/sb_0-17604105-1452827438.0/rpm/BUILD/mysql-5.6.29/mysql-5.6.29/storage/innobase/buf/buf0buf.cc line 3691
InnoDB: Warning: a long semaphore wait:
--Thread 139665089767168 has waited at buf0buf.cc line 2576 for 302.00 seconds the semaphore:
S-lock on RW-latch at 0x7f0701de88c0 created in file buf0buf.cc line 1069
number of readers 0, waiters flag 0, lock_word: 100000
Last time read locked in file row0sel.cc line 3220
Last time write locked in file /export/home/pb2/build/sb_0-17604105-1452827438.0/rpm/BUILD/mysql-5.6.29/mysql-5.6.29/storage/innobase/buf/buf0buf.cc line 3691
InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
InnoDB: Pending preads 2, pwrites 0

这可能是什么问题导致的呢？读并发太高了？ mysql 从库

我在后面输出的内容中看到了这个

267.14 inserts/s, 149.65 updates/s, 0.00 deletes/s, 362984.67 reads/s

这个的意思是真的有 36 万的查询

4828 次点击
所在节点    MySQL
3 条回复
Infernalzero
2016-06-13 13:38:12 +08:00
LATEST DETECTED DEADLOCK 那段你没贴哪知道是什么原因
sujin190
2016-06-13 17:23:48 +08:00
@Infernalzero 没有这段啊。。不过有这个 INNODB MONITOR OUTPUT
tcsky
2016-06-13 21:58:39 +08:00
感觉这边提技术类问题回答的人越来越少了..

这是一个专为移动设备优化的页面（即为了让你能够在 Google 搜索结果里秒开这个页面），如果你希望参与 V2EX 社区的讨论，你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/285275

V2EX 是创意工作者们的社区，是一个分享自己正在做的有趣事物、交流想法，可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX