MySQL Bugs: #48517: InitialLogFileGroup causes ndb

Bug #48517	InitialLogFileGroup causes ndb_require
Submitted:	3 Nov 2009 21:48	Modified:	4 Nov 2009 15:32
Reporter:	Andrew Hutchings	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Disk Data	Severity:	S2 (Serious)
Version:		OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
Found this whilst figuring out bug#48516

Tested in 7.0.6 and 7.0.8a

With the following in config.ini:

InitialLogFileGroup=name=LG1; undo_buffer_size=128M; undo1.log:250M; undo2.log:150M

Time: Tuesday 3 November 2009 - 21:44:39
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: ndbcntr/NdbcntrMain.cpp
Error object: NDBCNTR (Line: 2088) 0x0000000a
Program: /home/linuxjedi/Programming/Builds/mysql-cluster-gpl-7.0.8a-linux-x86_64-glibc23/bin/ndbd
Pid: 27640
Version: mysql-5.1.37 ndb-7.0.8a
Trace: /home/linuxjedi/Desktop/issues/41505/ndb/

How to repeat:
Attempt to start node

Logs and config.ini attached shortly

Logs and config file

Attachment: bug48517-logs.tar.gz (application/x-gzip, text), 53.52 KiB.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/89276

3191 Jonas Oreland	2009-11-04
      ndb - bug#48517 - fix proper error message when failing to commit schema trans during initial start

I changed so that error code comes out in error-log
(in your case error 1504)
> perror --ndb 1504
NDB error code 1504: Out of logbuffer memory: Permanent error: Schema error

Documented bugfix in the NDB-7.0.10 changelog as follows:

        NDB failed to provide a valid error message it failed to commit
        schema transactions during an initial start when the cluster was
        configured using the InitialLogFileGroup parameter.

Closed.