Author: js221926
Date: 2011-06-29 12:01:55 +0200 (Wed, 29 Jun 2011)
New Revision: 26642
Log:
Cluster BUG#61684:
Changelog entry
Updated descriptions for MaxNoOfTables and MaxNoOfAttributes
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
trunk/dynamic-docs/command-optvars/ndb-config-params.xml
trunk/refman-5.0/mysql-cluster-configuration-core.xml
trunk/refman-5.1/mysql-cluster-configuration-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2011-06-29 08:51:04 UTC (rev 26641)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2011-06-29 10:01:55 UTC (rev 26642)
Changed blocks: 1, Lines Added: 37, Lines Deleted: 0; 1540 bytes
@@ -9,6 +9,43 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="61684"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.56-ndb-6.3.45"/>
+ <version ver="5.1.56-ndb-7.0.26"/>
+ <version ver="5.1.56-ndb-7.1.15"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Handling of the
+ <literal role="ndbparam:ndbd">MaxNoOfTables</literal> and
+ <literal role="ndbparam:ndbd">MaxNoOfAttributes</literal>
+ configuration parameters was not consistent in all parts of the
+ <literal role="se">NDB</literal> kernel, and were only strictly
+ enforced by the <literal>DBDICT</literal> and
+ <literal>SUMA</literal> kernel blocks. This could lead to
+ problems when tables could be created but not replicated. Now
+ these parameters are treated by <literal>SUMA</literal> and
+ <literal>DBDICT</literal> as suggested maximums rather than hard
+ limits, as they are elsewhere in the
+ <literal role="se">NDB</literal> kernel.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="clusterapi"/>
<manual type="NdbTransaction"/>
<manual type="refresh()"/>
Modified: trunk/dynamic-docs/command-optvars/ndb-config-params.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/ndb-config-params.xml 2011-06-29 08:51:04 UTC (rev 26641)
+++ trunk/dynamic-docs/command-optvars/ndb-config-params.xml 2011-06-29 10:01:55 UTC (rev 26642)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 981 bytes
@@ -2336,8 +2336,8 @@
<name>MaxNoOfAttributes</name>
<shortdescription>
- Total number of attributes stored in database (sum over all
- tables)
+ Suggests a total number of attributes stored in database (sum over
+ all tables)
</shortdescription>
<values vartype="numeric" platform="all" inversion="4.1.3" units="integer">
@@ -2755,7 +2755,7 @@
<name>MaxNoOfTables</name>
<shortdescription>
- Total number of tables stored in the database
+ Suggests a total number of NDB tables stored in the database
</shortdescription>
<values vartype="numeric" platform="all" inversion="4.1.3" units="integer">
Modified: trunk/refman-5.0/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-configuration-core.xml 2011-06-29 08:51:04 UTC (rev 26641)
+++ trunk/refman-5.0/mysql-cluster-configuration-core.xml 2011-06-29 10:01:55 UTC (rev 26642)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 4; 2806 bytes
@@ -2595,11 +2595,23 @@
<para condition="dynamic:optvar:item" role="5.0:ndb-config-params:maxnoofattributes-ndbd"/>
<para>
- Defines the number of attributes that can be defined in the
- cluster.
+ This parameter sets a suggested maximum number of attributes
+ that can be defined in the cluster; like
+ <literal role="ndbparam:ndbd">MaxNoOfTables</literal>, it is
+ not intended to function as a hard upper limit.
</para>
<para>
+ A known issue in MySQL Cluster in MySQL ¤t-series; is
+ that this parameter is occasionally treated as a hard limit
+ for certain operations. This can lead to confusion when it
+ is sometimes possible (or not possible, depending on the
+ circumstances) to create more than
+ <literal>MaxNoOfAttributes</literal> attributes. This is
+ fixed in MySQL Cluster NDB 6.3 and later. (Bug #61684)
+ </para>
+
+ <para>
The default value is 1000, with the minimum possible value
being 32. The maximum is 4294967039. Each attribute consumes
around 200 bytes of storage per node due to the fact that
@@ -2656,11 +2668,24 @@
<para>
A table object is allocated for each table and for each
- unique hash index in the cluster. This parameter sets the
- maximum number of table objects for the cluster as a whole.
+ unique hash index in the cluster. This parameter sets a
+ suggested maximum number of table objects for the cluster as
+ a whole; like
+ <literal role="ndbparam:ndbd">MaxNoOfAttributes</literal>,
+ it is not intended to function as a hard upper limit.
</para>
<para>
+ A known issue in MySQL Cluster in MySQL ¤t-series; is
+ that this parameter is occasionally treated as a hard limit
+ for certain operations. This can lead to confusion when it
+ is sometimes possible (or not possible, depending on the
+ circumstances) to create more than
+ <literal>MaxNoOfTables</literal> tables. This is fixed in
+ MySQL Cluster NDB 6.3 and later. (Bug #61684)
+ </para>
+
+ <para>
For each attribute that has a
<literal role="type">BLOB</literal> data type an extra table
is used to store most of the
Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml 2011-06-29 08:51:04 UTC (rev 26641)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml 2011-06-29 10:01:55 UTC (rev 26642)
Changed blocks: 2, Lines Added: 32, Lines Deleted: 4; 3011 bytes
@@ -3758,11 +3758,25 @@
<para condition="dynamic:optvar:item" role="5.1:ndb-config-params:maxnoofattributes-ndbd"/>
<para>
- Defines the number of attributes that can be defined in the
- cluster.
+ This parameter sets a suggested maximum number of attributes
+ that can be defined in the cluster; like
+ <literal role="ndbparam:ndbd">MaxNoOfTables</literal>, it is
+ not intended to function as a hard upper limit.
</para>
<para>
+ Prior to MySQL Cluster NDB 6.3.45, MySQL Cluster NDB 7.0.26,
+ and MySQL Cluster NDB 7.1.15, this parameter was sometimes
+ treated as a hard limit for certain operations. This caused
+ problems with MySQL Cluster Replication, when it was
+ possible to create more tables than could be replicated, and
+ sometimes led to confusion when it was possible (or not
+ possible, depending on the circumstances) to create more
+ than <literal>MaxNoOfAttributes</literal> attributes. (Bug
+ #61684)
+ </para>
+
+ <para>
The default value is 1000, with the minimum possible value
being 32. The maximum is 4294967039. Each attribute consumes
around 200 bytes of storage per node due to the fact that
@@ -3823,11 +3837,25 @@
<para>
A table object is allocated for each table and for each
- unique hash index in the cluster. This parameter sets the
- maximum number of table objects for the cluster as a whole.
+ unique hash index in the cluster. This parameter sets a
+ suggested maximum number of table objects for the cluster as
+ a whole; like
+ <literal role="ndbparam:ndbd">MaxNoOfAttributes</literal>,
+ it is not intended to function as a hard upper limit.
</para>
<para>
+ Prior to MySQL Cluster NDB 6.3.45, MySQL Cluster NDB 7.0.26,
+ and MySQL Cluster NDB 7.1.15, this parameter was sometimes
+ treated as a hard limit for certain operations. This caused
+ problems with MySQL Cluster Replication, when it was
+ possible to create more tables than could be replicated, and
+ sometimes led to confusion when it was possible (or not
+ possible, depending on the circumstances) to create more
+ than <literal>MaxNoOfTables</literal> tables.
+ </para>
+
+ <para>
For each attribute that has a
<literal role="type">BLOB</literal> data type an extra table
is used to store most of the
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r26642 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.0 refman-5.1 | jon.stephens | 29 Jun |
