Author: jstephens
Date: 2007-03-23 10:53:07 +0100 (Fri, 23 Mar 2007)
New Revision: 5517
Log:
Documenting Cluster/General bugfixes:
Bug #26515, Bug #19378, Bug #21296, Bug #26825, Bug #27003,
Bug #27087, Bug #27203, Bug #27283, Bug #27286, Bug #27291
Plus some misc.fixes.
Modified:
trunk/ndbapi/ndb-classes.xml
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/ndbapi/ndb-classes.xml
===================================================================
--- trunk/ndbapi/ndb-classes.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/ndbapi/ndb-classes.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 559 bytes
@@ -1924,7 +1924,7 @@
<row>
<entry><literal>get_next_ndb_object()</literal></entry>
<entry><para>
- Used iterate through mutliple <literal>Ndb</literal>
+ Used to iterate through multiple <literal>Ndb</literal>
objects.
</para>
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 8; 1607 bytes
@@ -8304,16 +8304,10 @@
downgrading a MySQL Cluster from one MySQL release to another. It
discusses different types of Cluster upgrades and downgrades, and
provides a Cluster upgrade/downgrade compatibility matrix (see
- <xref
- linkend="mysql-cluster-upgrade-downgrade-compatibility"/>).
- </para>
-
- <para>
- <emphasis role="bold">Important</emphasis>: You are expected
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected
already to be familiar with installing and configuring a MySQL
Cluster prior to attempting an upgrade or downgrade. See
- <xref
- linkend="mysql-cluster-configuration"/>.
+ <xref linkend="mysql-cluster-configuration"/>.
</para>
<para>
@@ -8498,6 +8492,16 @@
may be restarted using the <command>ndb_mgm</command> management
client <literal>RESTART</literal> command.
</para>
+
+ <important>
+ <para>
+ When performing an upgrade or downgrade of the cluster
+ software, you <emphasis>must</emphasis> upgrade or downgrade
+ the management nodes <emphasis>first</emphasis>, then the data nodes, and finally
+ the SQL nodes. Doing so in any other order may leave the
+ cluster in an unusable state.
+ </para>
+ </important>
</section>
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 9; 1790 bytes
@@ -8330,22 +8330,16 @@
<primary>downgrades</primary>
<secondary>MySQL Cluster</secondary>
</indexterm>
-
+
<para>
This portion of the MySQL Cluster chapter covers upgrading and
downgrading a MySQL Cluster from one MySQL release to another. It
discusses different types of Cluster upgrades and downgrades, and
provides a Cluster upgrade/downgrade compatibility matrix (see
- <xref
- linkend="mysql-cluster-upgrade-downgrade-compatibility"/>).
- </para>
-
- <para>
- <emphasis role="bold">Important</emphasis>: You are expected
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected
already to be familiar with installing and configuring a MySQL
Cluster prior to attempting an upgrade or downgrade. See
- <xref
- linkend="mysql-cluster-configuration"/>.
+ <xref linkend="mysql-cluster-configuration"/>.
</para>
<para>
@@ -8530,6 +8524,16 @@
may be restarted using the <command>ndb_mgm</command> management
client <literal>RESTART</literal> command.
</para>
+
+ <important>
+ <para>
+ When performing an upgrade or downgrade of the cluster
+ software, you <emphasis>must</emphasis> upgrade or downgrade
+ the management nodes <emphasis>first</emphasis>, then the data nodes, and finally
+ the SQL nodes. Doing so in any other order may leave the
+ cluster in an unusable state.
+ </para>
+ </important>
</section>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 1, Lines Added: 38, Lines Deleted: 0; 1680 bytes
@@ -76,6 +76,44 @@
</para>
<itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: It was not possible to set
+ <literal>LockPagesInMainMemory</literal> equal to
+ <literal>0</literal>. (Bug #27291)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A race condition could sometimes occur if the node
+ acting as master failed while node IDs were still being
+ allocated during startup. (Bug #27286)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When a data node was taking
+ over as the master node, a race condition could sometimes
+ occur as the node was assuming responsibility for handling of
+ global checkpoints. (Bug #27283)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <command>mysqld</command> processes would sometimes crash
+ under high load. (Bug #26825)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Some values of <literal>MaxNoOfTables</literal>
+ caused the error <errortext>Job buffer congestion</errortext>
+ to occur. (Bug #19378)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 9; 1789 bytes
@@ -8453,22 +8453,16 @@
<primary>downgrades</primary>
<secondary>MySQL Cluster</secondary>
</indexterm>
-
+
<para>
This portion of the MySQL Cluster chapter covers upgrading and
downgrading a MySQL Cluster from one MySQL release to another. It
discusses different types of Cluster upgrades and downgrades, and
provides a Cluster upgrade/downgrade compatibility matrix (see
- <xref
- linkend="mysql-cluster-upgrade-downgrade-compatibility"/>).
- </para>
-
- <para>
- <emphasis role="bold">Important</emphasis>: You are expected
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected
already to be familiar with installing and configuring a MySQL
Cluster prior to attempting an upgrade or downgrade. See
- <xref
- linkend="mysql-cluster-configuration"/>.
+ <xref linkend="mysql-cluster-configuration"/>.
</para>
<para>
@@ -8653,6 +8647,16 @@
may be restarted using the <command>ndb_mgm</command> management
client <literal>RESTART</literal> command.
</para>
+
+ <important>
+ <para>
+ When performing an upgrade or downgrade of the cluster
+ software, you <emphasis>must</emphasis> upgrade or downgrade
+ the management nodes <emphasis>first</emphasis>, then the data nodes, and finally
+ the SQL nodes. Doing so in any other order may leave the
+ cluster in an unusable state.
+ </para>
+ </important>
</section>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-23 09:45:55 UTC (rev 5516)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-23 09:53:07 UTC (rev 5517)
Changed blocks: 1, Lines Added: 73, Lines Deleted: 0; 2747 bytes
@@ -231,6 +231,79 @@
</para>
<itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: It was not possible to set
+ <literal>LockPagesInMainMemory</literal> equal to
+ <literal>0</literal>. (Bug #27291)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A race condition could sometimes occur if the node
+ acting as master failed while node IDs were still being
+ allocated during startup. (Bug #27286)
+ </para>
+ </listitem>
+
+
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When a data node was taking
+ over as the master node, a race condition could sometimes
+ occur as the node was assuming responsibility for handling of
+ global checkpoints. (Bug #27283)
+ </para>
+ </listitem>
+
+
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A delete operation using a scan following by an insert using
+ a scan could cause a data node to fail. (Bug #27203)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The same failed request from
+ an API node could be handled by the cluster multiple times,
+ resulting in reduced performance. (Bug #27087)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The failure of a data node while restarting could cause
+ other data nodes to hang or crash. (Bug #27003)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <command>mysqld</command> processes would sometimes crash
+ under high load. (Bug #26825)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When performing an upgrade or
+ downgrade, no specific error information was made available
+ when trying to upgrade data nodes or SQL nodes before
+ upgrading management nodes. (Bug #21296)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Some values of <literal>MaxNoOfTables</literal>
+ caused the error <errortext>Job buffer congestion</errortext>
+ to occur. (Bug #19378)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5517 - in trunk: ndbapi refman-4.1 refman-5.0 refman-5.1 | jon | 23 Mar |
