Bug #61684 Failed to create tables
Submitted: 29 Jun 2011 7:35 Modified: 29 Jun 2011 10:02
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[29 Jun 2011 7:35] Jonas Oreland 
Description:
Due to bug#47793, MaxNoOfTables aren't strictly enforced.
But, SUMA allocates exactly MaxNoOfTables.
This leads to that one can create table for which one can't setup replication
This leads to weirdness in mysql.

This bug therefor "introduces" bug#47793 also in SUMA,
so that it's handled the same atleast.

How to repeat:
.

Suggested fix:
.
[29 Jun 2011 8:34] Jonas Oreland 
pushed to 6.3.45, 7.0.27 and 7.1.15
[29 Jun 2011 9:02] Jonas Oreland 
that should be 7.0.26
[29 Jun 2011 10:02] Jon Stephens 
Documented as follows in the NDB 6.3.45, 7.0.26, and 7.1.15 changelogs:

        Handling of the MaxNoOfTables and MaxNoOfAttributes
        configuration parameters was not consistent in all parts of the
        NDB kernel, and were only strictly enforced by the DBDICT and
        SUMA kernel blocks. This could lead to problems when tables
        could be created but not replicated. Now these parameters are
        treated by SUMA and DBDICT as suggested maximums rather than
        hard limits.

Also added a note to the descriptions of MaxNoOfTables and MaxNoOfAttributes.

Closed.