Bug #25708 Doing an alter table from myisam to ndb tablespace crashes data node
Submitted: 18 Jan 2007 22:12 Modified: 18 Feb 2007 23:41
Reporter: Bugs System Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S2 (Serious)
Version:5.1.14 OS:Linux (RHEL4.4 x86_64)
Assigned to: CPU Architecture:Any
Tags: alter, cluster, crash, data node, disk

[18 Jan 2007 22:12] Bugs System
Description:
Altering a 100k record table from MyISAM to ndbcluster on disk tablespace causes the datanode the query is from from to crash and output the error message below. The table was previously of ndbcluster on disk tablespace type.

Current byte-offset of file-pointer is: 1067

Time: Wednesday 17 January 2007 - 17:29:48
Status: Unknown
Message: No message slogan found (please report a bug if you get this error code) (Unknown)
Error: 0
Error data: We(6) have been declared dead by 7 reason: Hearbeat failure(4)
Error object: QMGR (Line: 2914) 0x0000000e
Program: ndbd
Pid: 20248
Trace: /data/ndb_6_trace.log.1
Version: Version 5.1.14 (beta)
***EOM***

Time: Wednesday 17 January 2007 - 17:31:48
Status: Temporary error, restart node
Message: WatchDog terminate, internal error or massive overload on the machine running this node (Internal error, programming error or missing error message, please report a bug)
Error: 6050
Error data: Job Handling
Error object: WatchDog.cpp
Program: ndbd
Pid: 20248
Trace: /data/ndb_6_trace.log.2
Version: Version 5.1.14 (beta)
***EOM***

How to repeat:
If I run: "alter table 1_610_SMTP TABLESPACE ts_01 STORAGE DISK ENGINE NDB;".
[18 Jan 2007 23:09] Jonas Oreland
Hi,

Please upload config.ini, clusterlog and error/trace files
(and maybe your schema, if it could be schema related...)

/jonas
[18 Jan 2007 23:41] Miguel Solorzano
Changing status to Need Feedback according Jonas last comment.
[19 Feb 2007 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".