MySQL Bugs: #53540: ndbmtd will not stay up

Bug #53540	ndbmtd will not stay up
Submitted:	10 May 2010 14:29	Modified:	30 Sep 2010 11:09
Reporter:	Richard McCluskey	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1-telco-7.0	OS:	Linux (2.6.18-164.11.1.el5 CentOS 5.4)
Assigned to:		CPU Architecture:	Any
Tags:	Version: mysql-5.1.39 ndb-7.0.9b

Description:
Data node disconnects with following error:

Time: Saturday 8 May 2010 - 12:35:46
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/DbtupExecQuery.cpp
Error object: DBTUP (Line: 3808) 0x0000000a
Program: ndbmtd
Pid: 11443 thr: 4
Version: mysql-5.1.39 ndb-7.0.9b
Trace: /var/lib/mysql/ndb_4_trace.log.2 /var/lib/mysql/ndb_4_trace.log.2_t1 /var/lib/mysql/ndb_4_trace.log.2_t2 /var/lib/mysql/nd

How to repeat:
dont know

trace/log-files ? (ndb_error_reporter)

Bug-data-53540.tar.gz uploaded to ftp.mysql.com/pub/mysql/upload

Node now will not come back up at all. When it does come up it gets to a point where the memory reports bigger data usage than the other node, then it errors ...
I understand though that this may just be the memory reporting error mentioned earlier, but thought I'd better add that info just in case

CORRECTION CORRECTION :

Bug-data-53540.tar.bz2 uploaded to ftp.mysql.com/pub/mysql/upload . It is a bz2 file not a .gz file. (just in case you are doing a C&P search!)

Hi,

The problem is that it runs out of UNDO when syncing with other node.
This can be fixed by increasing size of UNDO by issuing "alter logfile group add undofile" on the alive part of the cluster.

Did you manage to get node 4 to start ?

/Jonas

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".