Bug #22548 Data nodes fail during starting if MaxNoOfUniqueHashIndexes has upper limit
Submitted: 21 Sep 2006 13:31 Modified: 6 Dec 2006 10:23
Reporter: Serge Kozlov Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1.12 (beta) OS:
Assigned to: david li CPU Architecture:Any

[21 Sep 2006 13:31] Serge Kozlov
If config.ini has MaxNoOfUniqueHashIndexes = 4294967039 then ndbd nodes can't start with following message:

Time: Thursday 21 September 2006 - 14:07:06
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 object: NDBCNTR (Line: 1718) 0x0000000e
Program: /home/ndbdev/skozlov/builds/libexec/ndbd
Pid: 30494
Trace: /home/ndbdev/skozlov/builds/mysql-test/var/ndbcluster-config-testing/ndb_
Version: Version 5.1.12 (beta)

How to repeat:
1. Add to config ini MaxNoOfUniqueHashIndexes = 4294967039
2. Start cluster
3. Look ndb_X_error.lo files

Suggested fix:
Probably should be correct error message like "memory allocation failure"
[21 Sep 2006 13:31] Serge Kozlov
Error log files and config.ini

Attachment: bugMaxNoOfUniqueHashIndexes.Max.zip (application/x-zip-compressed, text), 1.54 KiB.

[28 Sep 2006 11:16] 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.2293, 2006-09-28 19:17:37+08:00, dli@dev3-76.dev.cn.tlan +3 -0
  fixed for BUG#22548, added exit error messages when error occured during table creation.
[6 Dec 2006 10:23] 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


Documented bugfix in 5.1.14 changelog.

David, thanks for the paste.