Bug #24227 ndb_size.pl should report default values instead of < default for config params
Submitted: 12 Nov 2006 15:36 Modified: 30 Apr 2007 7:47
Reporter: Stewart Smith 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: Stewart Smith CPU Architecture:Any

[12 Nov 2006 15:36] Stewart Smith
On Fri, 2006-11-10 at 11:31 -0500, Johan Andersson wrote:
I suggest to change the ndb_size.pl script so that it defaults to the 
> "default value" of the Parameter settings it suggest, if the calculated 
> parameter by ndb_size.pl is less than the default value for that parameter.
> That would make me feel more comfortable in order to avoid users running 
> with too small values, and often untested combinations.
> $LOCATION is just one example where this happened, where they took the value 
> given by ndb_size.pl (MaxNoOfTables=10), and it failed miserably!
> If the ndb_size.pl returns the default value in such a case, then it 
> would be, as i said, better!

How to repeat:
use ndb_size.pl on small db

Suggested fix:
see above
[24 Apr 2007 20:53] Stewart Smith
part of Bug #24228 fix.

pushed to 5.1-ndb
[28 Apr 2007 19:35] Bugs System
Pushed into 5.1.18-beta
[30 Apr 2007 7:47] 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,18 changelog.