Bug #68961 | mysql replication hangs | ||
---|---|---|---|
Submitted: | 15 Apr 2013 9:04 | Modified: | 24 Dec 2013 15:55 |
Reporter: | Michal Grzedzicki | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.5.28 | OS: | Linux (64 bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | btr_search_latch, deadlock, innodb, latch, mysqld |
[15 Apr 2013 9:04]
Michal Grzedzicki
[15 Apr 2013 9:05]
Michal Grzedzicki
gdb trace output
Attachment: mysql_gdb.txt (text/plain), 92.01 KiB.
[15 Apr 2013 17:57]
Sveta Smirnova
Thank you for the report. GDB backtrace shows some optimization of queries running. To prove this is MySQL bug we need repeatable test case. Do you have some job running once per week on slaves in time when you observer this behavior?
[15 Apr 2013 21:11]
Michal Grzedzicki
trace from another machine with same problem
Attachment: mysql_gdb2.txt (text/plain), 69.21 KiB.
[15 Apr 2013 21:25]
Sveta Smirnova
Thank you for the feedback. Do you have some job running once per week on one of affected machines in time when you observer this behavior?
[15 Apr 2013 21:30]
Michal Grzedzicki
no there are no cronjobs running when the database hangs, deadlocks aren't periodical, it seems to happen more if there is more traffick on the site
[25 Apr 2013 19:59]
Sveta Smirnova
Thank you for the feedback. This still looks more like support request for me. For example, such issue can happen if you have problems with disk or not best tuned InnoDB options, some of queries can affect this. For start: please check if you did not set innodb_lock_wait_timeout to value larger than its's default 50 seconds and check output of SHOW ENGINE INNODB STATUS and SHOW FULL PROCESSLIST during problem time. Pay attention for queries and transactions in blocked state, check if slave SQL thread involved (since you see this on slaves only).
[6 May 2013 10:25]
Michal Grzedzicki
innodb_lock_wait_timeout is a litle higher (80) then the default 50 The deadlock persists for much more the this. The database is completly unresponsive. I can't send any command to the database, eg. show processlist All the threads are waiting for locks. I think btr_search_latch which deadlock here is not the lock refered in innodb_lock_wait_timeout.
[19 Sep 2013 17:29]
MySQL Verification Team
http://bugs.mysql.com/bug.php?id=62018 !
[24 Dec 2013 15:55]
Sveta Smirnova
Shane, thank you for the bug #. I will set this report as duplicate of bug #62018 for now, but we need to check it one more time when bug #62018 is fixed.