Bug #45062 | Stuck threads needing a "killall -9 mysqld" | ||
---|---|---|---|
Submitted: | 25 May 2009 9:33 | Modified: | 29 Dec 2009 19:50 |
Reporter: | Anton Dischner | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.1.34 | OS: | Linux (SLES10 x86 64bit SP2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | hanging, innodb, mysqld, stuck thread |
[25 May 2009 9:33]
Anton Dischner
[25 May 2009 10:18]
Sveta Smirnova
Thank you for the report. Please provide full error log file, output of SHOW PROCESSLIST in time when problem occurs and real query and output of SHOW CREATE TABLES for all underlying tables,
[25 May 2009 10:19]
Sveta Smirnova
Link to the forum with more description about the problem: http://forums.mysql.com/read.php?22,263084,263084#msg-263084
[26 May 2009 14:06]
Anton Dischner
In my first post i wrote: There where no table locks. (checked with innotop) I have to corret this. There -are- table locks as seen in file locks.txt This time the locks timed out and the process continued. Have to wait for another appearence, regards, Toni
[28 May 2009 11:46]
Anton Dischner
I changed init variables to reflect our # of tables, old was 512 inspired by MySQL 5.4 changes the default of them. Would love to test 5.4 here, are there SuSE 64 RPMs in the pipeline? Current table_open_cache = 1024 tables Current table_definition_cache = 1024 tables You have a total of 832 tables You have 862 open tables. No stuck threads so far. Still testing.
[2 Jun 2009 10:38]
Anton Dischner
Tuning of parameters didn't help. Had same issue this morning. Stuck process which blocks others until they time out. Blocking process itself clears after about another 1200 s. We reviewed the problem and found no error on our side. We have to go back to MySQL 5.0.51a if we find no solution in this bugreport. kind regards, A. Dischner
[3 Jun 2009 14:10]
Anton Dischner
We decided to go back to MySQL 5.0.51a Please close this bugreport, regards, A. Dischner
[8 Jun 2009 7:02]
Sveta Smirnova
Thank you for the feedback. We'd like to not close the report until it is proved this is not MySQL bug or fixed, although I can not repeat described behavior with generic tests. Please provide your configuration file also: probably some variables matter.
[8 Jun 2009 9:24]
Anton Dischner
Our MySQL 5.1 installation is no longer available.
[29 Dec 2009 19:50]
Sveta Smirnova
Thank you for the feedback. You have option innodb_lock_wait_timeout = 1200 in the my.cnf. In this case query will wait lock for 1200 seconds before it fails with "ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction". Having query locked is expected, because you update the table in parallel.