Bug #26454 LockPagesInMemory=1 is called after distributed communcation has started
Submitted: 16 Feb 2007 17:09 Modified: 26 Feb 2007 2:22
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0,5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[16 Feb 2007 17:09] Jonas Oreland 
Description:
This makes it somewhat likely that a node can die due to missed heartbeat real early

How to repeat:
 

Suggested fix:
[16 Feb 2007 17:11] 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:

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

ChangeSet@1.2285, 2007-02-16 18:10:27+01:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#26454
    make lockpages=1 run a bit earlier in startup
[16 Feb 2007 17:32] Jonas Oreland 
pushed into 5.0-ndb, 5.1-ndb, and 5.1-telco
[21 Feb 2007 15:20] Tomas Ulin 
5.1.16 5.0.37 ndb-6.1.3
[26 Feb 2007 2:22] 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

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

Documented bugfix in 5.0.38, 5.1.16, and ndb-6.1.3 changelogs.