Description:
Setting the LockPagesInMainMemory to 1 doesn't allow the data nodes to come up. The
data/index memory is 80MB and 10MB with about 700MB free available memory. Starting 5.0.37
2 data nodes makes the machine for a short moment frozen as it consumes, it seems,
completely the free memory.

Also, setting LockPagesInMainMemory to 0 (zero) is not allowed.

How to repeat:
Attached are the logs and the config.ini to show the problem. Just start the ndb_mgm and
the ndbds.

Suggested fix:
Might be a merge problems from MySQL 5.1?

Configuration file used

Attachment: config50.ini (application/octet-stream, text), 468 bytes.

Goes worse with value of two: LockPagesInMainMemory=2.

OK, the LockPagesInMainMemory was a simple 'getting out of memory'. Each ndbd process took
over 400Mb, and that's not possible to allocated with 700Mb free of course :)

Opened report a bit to fast there.

Anyway, LockPagesInMainMemory=0 doesn't work still. This needs a fix.

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/22363

ChangeSet@1.2297, 2007-03-20 16:08:39+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27291
    Fix correct min-value for LockPagesInMemory

pushed to 5.0-ndb, 51-ndb, telco-6.1 & 51-telco

Fixed in 5.0.40 and 5.1.17

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

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.0.40, 5.1.17, and ndb-6.1.6 changelogs.