Bug #43563 mysql-cluster NDB node crasch during optimize table
Submitted: 11 Mar 2009 14:55 Modified: 7 May 2009 5:43
Reporter: Alexandr Seidl Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S2 (Serious)
Version:mysql-5.1.30 ndb-6.3.20-GA OS:Linux
Assigned to: Assigned Account CPU Architecture:Any
Tags: ndbd

[11 Mar 2009 14:55] Alexandr Seidl
Description:
Time: Wednesday 11 March 2009 - 08:07:24
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: dbtup/DbtupVarAlloc.cpp
Error object: DBTUP (Line: 482) 0x0000000a
Program: /usr/local/mysql/bin/ndbd
Pid: 4769
Trace: /var/lib/mysql-cluster/ndb_12_trace.log.7
Version: mysql-5.1.30 ndb-6.3.20-GA
***EOM***

Trace log is awaileble on http://www.resal.cz:/ndb_12_trace.log.7

How to repeat:
it is not tested
[11 Mar 2009 15:09] Jonas Oreland
this is during an "optimize table" right?

can you upload
1) schema
2) *full* error reporter (as produced by ndb_error_reporter)
3) information about which table that optimize table was running at
   (logs says that it's table 260, but it's not trivial to map to SQL table)
4) information about how many rows are present it table being optimized

/Jonas
[13 Mar 2009 9:18] Jonas Oreland
this is a important bug,
but it's nor possible to proceed with information given so far.
therefor setting P2
[7 Apr 2009 5:43] Jonas Oreland
Hi again,

I'm going to put this bug into need-feedback.
Cause I need feedback/more info.
[7 May 2009 23: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".