Bug #45544 items with "freeing items" and "Sending data" never finish
Submitted: 17 Jun 2009 2:11 Modified: 13 Jul 2009 6:24
Reporter: Ala'a Ibrahim Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.1.34-community-log MySQL Community Ser OS:Linux
Assigned to: CPU Architecture:Any
Tags: freeing items, lock, sending data, Stuck

[17 Jun 2009 2:11] Ala'a Ibrahim
Description:
In one of the servers we have an issue that happens to one of the servers that some items that have the status of "freeing items" and "Sending data" are just stuck there, causing a lot of locks on the server, and the load of the server drops to almost 0.

The server then wouldn't restart, and the only solution is to kill the mysqld process, and fix the crashed tables that result from the kill.

How to repeat:
There is no specific knowledge of when does this happens or why, but it happens like once every 3 days.
[17 Jun 2009 5:21] Sveta Smirnova
Thank you for the report.

Do you have query cache enabled? Do you use InnoDB tables? See last comment to bug #42951 if so and check if suggestion solves your problem.
[17 Jun 2009 7:32] Mohammad Lahlouh
I'm from ala'a team

this is vbulletin system, all tables is myisam, and only one table innodb (session table).

we configured innodb to work as memory, innodb data file and log files store in memory partition for more performance.

Query cache is enabled.

I'll attache my.cnf file.

we've 32GB RAM.
[17 Jun 2009 7:32] Mohammad Lahlouh
my.cnf

Attachment: my.conf (application/octet-stream, text), 1.83 KiB.

[17 Jun 2009 8:12] Sveta Smirnova
Thank you for the feedback.

Please try to turn query cache off and test if it solves the problem: this can be duplicate of bug #43758
[17 Jun 2009 8:26] Mohammad Lahlouh
Thank for your feedback

I turn query cache off, and I'll test.
[12 Jul 2009 7:50] Mohammad Lahlouh
It's fine till now.
[13 Jul 2009 6:24] Sveta Smirnova
Thank you for the feedback. 

Closed as duplicate of bug #43758. Please upgrade to version 5.1.36 where bug #43758 is fixed.