Bug #52980 MaxAllocate has no effect anymore
Submitted: 20 Apr 2010 12:24
Reporter: Magnus Blåudd Email Updates:
Status: Verified Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: 6.3.34

[20 Apr 2010 12:24] Magnus Blåudd
The config parameter MaxAllocate has no effect anymore, it's read from config.ini but no block is longer using the value in MySQL Cluster 6.2, 6.3 , 7.0 and 7.1.

How to repeat:

The parameter was previously used in DBTUP.

Suggested fix:
Make the MaxAllocate parameter deprecated and print a warning when found in config.ini.
[3 May 2021 20:01] Jon Stephens
Documented fix as follows in the NDB 8.0.27 changelog:

    The old MaxAllocate data node configuration parameter has no
    effect in any current version of NDB Cluster. As of this
    release, it is deprecated and subject to removal in a future NDB

Noted the deprecation in the parameter's description in the Manual.