Bug #54448 | Killed alter table query Thread refuses go away and seems 2 block backup attempt | ||
---|---|---|---|
Submitted: | 11 Jun 2010 23:49 | Modified: | 12 Jul 2010 19:18 |
Reporter: | Arun Ramakrishnan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.45 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | killed kill thread backup timout |
[11 Jun 2010 23:49]
Arun Ramakrishnan
[11 Jun 2010 23:50]
Arun Ramakrishnan
output of "mysqladmin variables"
Attachment: mysql.variables.txt (text/plain), 21.99 KiB.
[11 Jun 2010 23:52]
Arun Ramakrishnan
restarting the server would involve a bit of bureaucracy and disruption I would like to avoid.
[12 Jun 2010 8:29]
Valeriy Kravchuk
Please, read the manual, http://dev.mysql.com/doc/refman/5.0/en/kill.html, about KILL. It explains that KILL can NOT stop query/connection immediately. If you still think that thread hangs in Killed state longer than needed, please, check if the same happens with a newer version of MySQL server, 5.0.90. We do not fix bugs that are repeatable only in older versions in any case.
[12 Jun 2010 17:51]
Arun Ramakrishnan
its still in Killed state. definitely more than 24 hours now and it still wont go away and mysqldump is blocking cause of this.
[12 Jun 2010 19:18]
Valeriy Kravchuk
Does it happen with server version 5.0.90?
[12 Jul 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".