MySQL Bugs: #44135: restart fails if using suffiently big cluster/threads

Bug #44135	restart fails if using suffiently big cluster/threads
Submitted:	7 Apr 2009 12:34	Modified:	15 Apr 2009 3:33
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	7.0	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
If using "big" cluster,
i.e #fragments per table gets above a certain threshold, 
the DIH's on-disk table-definition gets big enough to occupy
2 pages.

In this case Ndbfs.cpp contains a 7.0 only regression
that causes only 1 page to be written.

How to repeat:
.

Suggested fix:
reported by Johan

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

2884 Jonas Oreland	2009-04-07
      ndb - bug#44135 - fix incorrectly placed goto, causing only page 1 to be written using using FsWriteReq::fsListOfPairs, used by DIH

Pushed into 5.1.32-ndb-7.0.5 (revid:jonas@mysql.com-20090407123537-ugb2nzyipo89x9cp) (version source revid:jonas@mysql.com-20090407123439-a817p89r7s4l1hkb) (merge vers: 5.1.32-ndb-7.0.5) (pib:6)

Documented bugfix in the NDB-7.0.5 changelog as follows:

        If  the number of fragments per table rises above a certain threshold, 
        the DBDIH kernel block's on-disk table-definition grows large
        enough to occupy 2 pages. However, in MySQL Cluster NDB 7.0, only 1 page
        was actually written, causing table definitions as stored on disk to be
        incomplete.