MySQL Bugs: #52980: MaxAllocate has no effect anymore

Bug #52980	MaxAllocate has no effect anymore
Submitted:	20 Apr 2010 12:24
Reporter:	Magnus Blåudd	Email Updates:
Status:	Verified	Impact on me:	None
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

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
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:
MCI

The parameter was previously used in DBTUP.

Suggested fix:
Make the MaxAllocate parameter deprecated and print a warning when found in config.ini.

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
    release.

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

Closed.