Bug #44047 | Cluster API node, All threads stuck in lock wait | ||
---|---|---|---|
Submitted: | 2 Apr 2009 16:01 | Modified: | 27 Dec 2009 9:23 |
Reporter: | Brown Casey | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S1 (Critical) |
Version: | mysql-5.1.30 ndb-6.3.20 | OS: | Linux (ubuntu 8.04 (ec2)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | cluster, lock wait |
[2 Apr 2009 16:01]
Brown Casey
[7 Apr 2009 14:27]
Valeriy Kravchuk
Thank you for the problem report. Please, send my.cnf from this node. Try to disable query cache and check if the problem is still repeatable after that.
[7 Apr 2009 15:17]
Brown Casey
query_cache_size set to 0 After some research, I will probably keep that setting as our app is very write heavy, and the cache is likely invalidated 99% of the time. I will post if the issue shows up again.
[7 Apr 2009 15:20]
Valeriy Kravchuk
Thank you. Please, inform about any results of your testing without query cache.
[7 Apr 2009 15:26]
Brown Casey
I should also mention that I just rebuilt from the latest source last week and am now running mysql-5.1.32 ndb-6.3.23
[24 Apr 2009 20:30]
Brown Casey
The issue appears to have been related to the query cache. I have encountered no hung SQL nodes and no segfaults since disabling it.
[27 Nov 2009 9:23]
Valeriy Kravchuk
So, I think, this problem was more a result of misconfiguration than of any bug in MySQL code. Do you agree?
[30 Nov 2009 15:30]
Casey Brown
That depends on if you expect the query cache to hang or segfault with high volumes of invalidations. In retrospect, I don't mind. It was a very efficient way of telling me that what I was doing was wrong.
[28 Dec 2009 0: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".