Bug #16359 | Cluster: Server API Crash upon query | ||
---|---|---|---|
Submitted: | 11 Jan 2006 2:54 | Modified: | 5 Aug 2010 21:10 |
Reporter: | Adam Dixon (Candidate Quality Contributor) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.0 | OS: | Linux (RHEL4 64bit) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | 5.0.15, mysql-cluster-ndb-7.0.6 |
[11 Jan 2006 2:54]
Adam Dixon
[12 Jan 2006 8:22]
Valeriy Kravchuk
Thank you for a problem report. Please, try to find a repeatable sequence of actions that demonstrates this crash. And, better, on a newer version. Your 5.0.15 is really old.
[24 Jan 2006 18:15]
Hartmut Holzgraefe
I tried to reproduce your EXPLAIN crash using "CREATE TABLE SubAccounts" as found on http://www.koders.com/sql/fid12F1624946C5DC40C71DEB3193D37C60A1CB3ED0.aspx (using google), but it worked fine for me without problems. As your gdb backtrace shows that the crash already happens in the parser state i think that it doesn't matter that i could not fill the table with data. You reported this bug for MySQL 5.0.15, can you try to reproduce this with a more current version? I'd also like to know whether you are using a server binary provided by us (and if so the actual package name if possible), or whether you compile yourself
[2 Feb 2006 2:56]
Adam Dixon
It seems that the problem only occurs when two different servers which run the same application at exactly the same time the server crashes. The applications run every 15minnutes, and I can make the server crash every single time if I have them run at the same time (ntp etc) However if i split them apart by 5 minutes they run perfectly ok. No problems. So I ran mysqld in gdb again, and waited for cron to run the script on each of the servers; Perhaps more backtrace output can help you. See my Attached file.
[2 Feb 2006 2:56]
Adam Dixon
bt full output
Attachment: 20060202gdb.txt (text/plain), 8.48 KiB.
[2 Feb 2006 6:34]
Adam Dixon
I did notice mentions of sql cache c files in the gdb backtrace, so I put SQL_NO_CACHE in the queries and I havent had a crash yet (both running at the same time and everything) This may also assist you.
[21 Feb 2006 7:42]
Valeriy Kravchuk
OK, so the problem may be query cache related... Please, send your my.cnf files content from the failing servers. And, for the third time, I ask you to try to reproduce this with a newer version, 5.0.18.
[22 Mar 2006 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".