Bug #27902 NDB nodes crash on import of data
Submitted: 17 Apr 2007 21:08 Modified: 17 Apr 2007 23:56
Reporter: Brian Moon Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.0.26 OS:Linux (Gentoo)
Assigned to: CPU Architecture:Any
Tags: cluster, crash

[17 Apr 2007 21:08] Brian Moon
We have triggers on tables in our main mysql server.  Those triggers insert ids into a queue table and then a script picks them and copies data from our main server (innodb/myisam) to our cluster.  I tested this for months before moving the servers to our production facility.  However, now when I enable the cron job, NDB nodes crash with the following in the error log:

Time: Tuesday 17 April 2007 - 14:45:51
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: 
Error object: DBLQH (Line: 18363) 0x0000000a
Program: ndbd
Pid: 6678
Trace: /var/lib/mysql-cluster/ndb_2_trace.log.2
Version: Version 5.0.26

I have restarted the nodes, but error happens again.  Could something have happened when the nodes were shut down to be moved?  I can start the nodes from scratch if I need to.  They are not being used by the production system yet.

How to repeat:
I have no idea.
[17 Apr 2007 21:09] Brian Moon
Error file from ndb_error_report

Attachment: ndb_error_report_20070417160049.tar.bz2 (application/octet-stream, text), 248.06 KiB.

[17 Apr 2007 23:56] Adam Dixon
Are you able to upgrade your installed version to the latest available? 5.0.26 is now missing many bugfixes related to cluster.

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.