Bug #48502 Several configuration parameters should not differ between DB nodes
Submitted: 3 Nov 2009 13:18
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.28
Triage: Triaged: D5 (Feature request) / R6 (Needs Assessment) / E6 (Needs Assessment)

[3 Nov 2009 13:18] Magnus Blåudd
Description:
There are quite a few configuration parameters for MySQL Cluster that can be set different for each DB node  but in fact should not be allowed to differ between nodes.

They are quite easily identified since their help text follow the pattern "Total number of XXX that can be defined in the system"

MaxNoOfTables
MaxNoOfOrderedIndexes
MaxNoOfUniqueHashIndexes
MaxNoOfIndexes
MaxNoOfConcurrentIndexOperations
MaxNoOfTriggers
and so on...

How to repeat:
MCI

Suggested fix:
Check that all of the idenitifed parameters are defined the same on all DB nodes. In case a value that differs found print a warning describing the problem, it should probably also be possible to turn on "Strict" more where the above warning is turned into an error.
[3 Nov 2009 13:21] Magnus Blåudd
We could probably also upgrade the values to the highest specified value.