Author: jstephens
Date: 2009-02-18 21:04:02 +0100 (Wed, 18 Feb 2009)
New Revision: 13831
Log:
Documented fix for Cluster Bug #42973
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-4.1/mysql-cluster-limitations.xml
trunk/refman-5.0/mysql-cluster-limitations.xml
trunk/refman-5.1/mysql-cluster-limitations.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-02-18 19:05:42 UTC (rev 13830)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-02-18 20:04:02 UTC (rev 13831)
Changed blocks: 1, Lines Added: 34, Lines Deleted: 0; 1337 bytes
@@ -9,6 +9,40 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="cluster"/>
+ <manual type="ndb_mgmd"/>
+ <manual type="connectstrings"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="42973"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.32-ndb-6.2.17"/>
+ <version ver="5.1.32-ndb-6.3.23"/>
+ <version ver="5.1.32-ndb-6.4.3"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When using multiple management servers and starting several API
+ nodes (possibly including one or more SQL nodes) whose
+ connectstrings listed the management servers in different order,
+ it was possible for 2 API nodes to be assigned the same node ID.
+ When this happened it was possible for an API node not to get
+ fully connected, consequently producing a number of errors whose
+ cause was not easily recognizable.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="securityfix"/>
<manual type="XML"/>
<manual type="XPath"/>
Modified: trunk/refman-4.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-limitations.xml 2009-02-18 19:05:42 UTC (rev 13830)
+++ trunk/refman-4.1/mysql-cluster-limitations.xml 2009-02-18 20:04:02 UTC (rev 13831)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 729 bytes
@@ -1389,6 +1389,12 @@
automatic allocation of node IDs does not work across
multiple management servers.
</para>
+
+ <para>
+ In addition, all API nodes (including MySQL servers acting
+ as SQL nodes), should list all management servers using
+ the same order in their connectstrings.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-limitations.xml 2009-02-18 19:05:42 UTC (rev 13830)
+++ trunk/refman-5.0/mysql-cluster-limitations.xml 2009-02-18 20:04:02 UTC (rev 13831)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 729 bytes
@@ -1372,6 +1372,12 @@
automatic allocation of node IDs does not work across
multiple management servers.
</para>
+
+ <para>
+ In addition, all API nodes (including MySQL servers acting
+ as SQL nodes), should list all management servers using
+ the same order in their connectstrings.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations.xml 2009-02-18 19:05:42 UTC (rev 13830)
+++ trunk/refman-5.1/mysql-cluster-limitations.xml 2009-02-18 20:04:02 UTC (rev 13831)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 862 bytes
@@ -1736,6 +1736,15 @@
</para>
</formalpara>
+
+ <para>
+ Also, when using multiple management servers and starting
+ concurrently several API nodes (possibly including one or
+ more SQL nodes) whose connectstrings listed the management
+ servers in different order, it was possible for 2 API nodes
+ to be assigned the same node ID. This issue is resolved in
+ MySQL Cluster NDB 6.2.17, 6.3.23, and 6.4.3. (Bug #42973)
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13831 - in trunk: dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 | jon.stephens | 18 Feb |
