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
Triage: Triaged: D4 (Minor) / R2 (Low) / E2 (Low)

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