Bug #27581 drop/truncate table can result in node/cluster-crash
Submitted: 2 Apr 2007 6:43 Modified: 10 Apr 2007 6:41
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1,5.0,5.1 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[2 Apr 2007 6:43] Jonas Oreland

How to repeat:

Suggested fix:
[2 Apr 2007 7:07] 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.2303, 2007-04-02 09:07:15+02:00, jonas@perch.ndb.mysql.com +1 -0
  ndb - bug#27581
    make sure not to leave partially initialized pagerage-records
[7 Apr 2007 7:00] Bugs System
Pushed into 5.0.40
[7 Apr 2007 7:01] Bugs System
Pushed into 5.1.18-beta
[10 Apr 2007 6: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


Documented bugfix in 5.0.40, 5.1.18, and telco-6.1.6 changelogs.
[29 Jun 2007 5:40] Jonas Oreland
when the node is running out pagerangerecord,
  it failed to free a 50% initialized record.
  this was however not noticed until drop/truncate table.

In order for this bug to happen you should:
- have had a full database, i.e get return code 827
  but still have datamemory (!= 100%)


This can be achived by setting MaxNoTables (and indexes...) very low
and setting DataMemory very high