The statement remained in the killed state for 2 hrs and then got out of the
processlist. Great sigh of relief then :).
Sorry for the late reply. But one thing I still couldn't understand is why
it took so long to move out of the processlist from the killed state.
sujay
-----Original Message-----
From: Gleb Paharenko [mailto:gleb.paharenko@stripped]
Sent: Sunday, October 16, 2005 12:53 AM
To: mysql@stripped
Subject: Re: Killing a thread -- Urgent
Hello.
Do you have other queries which are running at this moment on the server?
The show-processlist.html says that thread could be in Killed state if it is
locked by another thread.
What version of MySQL do you use? What storage engine does your table have?
Sujay Koduri <SujayK@stripped> wrot
>hi all..
>
>I started a select count(1) command on a table in mysql, assuming it
>will end soon within the off peak time..
>But now the peak load time is about to start, so i tried to kill that
>query..
>
>logged into mysql as root.
>show processlist for getting the thread id.
>kill 85300 (thrad_id)
>
>After doing this the state of the query has changed to killed, but
>still it is showing like this
>
>85300 | root | localhost | db_name | Killed | 23055 |
>Sending data | select count(1) from
>
>I have issued the kill command almost 1hour back..but still it is
>showing up this query..And the iowait on the DB server is touching
>60%..generally in off peak times it should be 35%. (i seriously suspect
>this query for the high iowaits)
>
>Any help is greatly appreciated.
>
>Thank you
>sujay
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1
