Bug #20065 Erroneous error message at Node Restart if MaxNoOfOrderedIndexes changed too low
Submitted: 25 May 2006 10:10 Modified: 6 Dec 2006 8:41
Reporter: Serge Kozlov Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.11 OS:Linux (Linux FC4)
Assigned to: Stewart Smith CPU Architecture:Any

[25 May 2006 10:10] Serge Kozlov
If an index data requires more MaxNoOfOrederedIndexes than it is defined in config.ini then data nodes can't restart and shows following error:

Current byte-offset of file-pointer is: 568

Time: Thursday 25 May 2006 - 12:02:07
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: dbdict/Dbdict.cpp
Error object: DBDICT (Line: 3153) 0x0000000a
Program: /home/ndbdev/skozlov/builds/libexec/ndbd
Pid: 24738
Trace: /space/run/ndb_3_trace.log.1
Version: Version 5.1.11 (beta)

How to repeat:
1. Create config.ini like that: 
NoOfReplicas: 2
DataDir: /space/run
FileSystemPath: /space/run
DataMemory: 300M
IndexMemory: 100M
MaxNoOfOrderedIndexes: 100

[mgm default]
ArbitrationRank: 1
DataDir: /space/run

Id: 1
HostName: ndb16

Id: 2
HostName: ndb16

Id: 3
HostName: ndb16

Id: 15
HostName: ndb16
2. Start cluster.
3. Run load_tpcb.pl ndb16 3306 root BLANK ndb
4. Wait while the script finished.
5. Change MaxNoOfOrderedIndexes: 0
6. Restart ndb_mgmd
7. Try to restart data node (X restart)
[25 May 2006 10:14] Serge Kozlov
trace, log files and config.ini

Attachment: bug20065.tar.gz (application/gzip, text), 57.43 KiB.

[3 Nov 2006 8:05] Bugs System
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:


ChangeSet@1.2338, 2006-11-03 19:05:09+11:00, stewart@willster.(none) +1 -0
  BUG#20065 Erroneous error message at Node Restart if MaxNoOfOrderedIndexes changed too low
  nicer error message to user, along with error code to help track down the problem.
[8 Nov 2006 4:21] Stewart Smith
pushed to 5.1-ndb
[6 Dec 2006 8:41] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at


Bugfix documented in 5.1.14 changelog.