Author: jstephens
Date: 2005-12-15 13:28:44 +0100 (Thu, 15 Dec 2005)
New Revision: 567
Log:
Documented Cluster bugfixes:
14828/15517 (5.0/5.1)
15632, 15685 (4.1/5.0)
15675 (5.0)
15682 (moved to 5.0.17 changelog; was erroneously placed under 5.0.18)
Modified:
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-12-15 11:10:18 UTC (rev 566)
+++ trunk/refman-common/news-4.1.xml 2005-12-15 12:28:44 UTC (rev 567)
@@ -182,6 +182,23 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal>: Under some circumstances, it
+ was possible for a restarting node to undergo a forced
+ shutdown. (Bug #15632)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: If an abort by the Transaction
+ Co-ordinator timed out, the abort condition was incorrectly
+ handled, causing the transacviton record to be released
+ prematurely. (Bug #15685)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: A node which failed during
cluster startup was sometimes not removed from the internal
list of active nodes. (Bug #15587)
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-12-15 11:10:18 UTC (rev 566)
+++ trunk/refman-common/news-5.0.xml 2005-12-15 12:28:44 UTC (rev 567)
@@ -208,24 +208,40 @@
<listitem>
<para>
- <literal>NDB Cluster</literal>: A node which failed during
- cluster startup was sometimes not removed from the internal
- list of active nodes. (Bug #15587)
+ <literal>NDB Cluster</literal>: Under some circumstances, it
+ was possible for a restarting node to undergo a forced
+ shutdown. (Bug #15632)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: Using <literal>ORDER
- BY <replaceable>primary_key_column</replaceable></literal>
- when selecting from a table having the primary key on a
- <literal>VARCHAR</literal> column caused a forced shutdown of
- the cluster. (Bug #15240, Bug #15682)
+ <literal>NDB Cluster</literal>: If an abort by the Transaction
+ Coordinator timed out, the abort condition was incorrectly
+ handled, causing the transaction record to be released
+ prematurely. (Bug #15685)
</para>
</listitem>
<listitem>
<para>
+ <literal>NDB Cluster</literal>: The
+ <literal>ndb_read_multi_range.test</literal> script failed to
+ drop a table, causing the test to fail. (Bug #15675) (See also
+ Bug #15401.)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A node which failed during
+ cluster startup was sometimes not removed from the internal
+ list of active nodes. (Bug #15587)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Resolution of the argument to the <literal>VALUES()</literal>
function to a variable inside a stored routine caused a server
crash. The argument must be a table column. (Bug #15441)
@@ -299,6 +315,16 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal>: Using <literal>ORDER
+ BY <replaceable>primary_key_column</replaceable></literal>
+ when selecting from a table having the primary key on a
+ <literal>VARCHAR</literal> column caused a forced shutdown of
+ the cluster. (Bug #14828, Bug #15240, Bug #15682, Bug #15517)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Under certain circumstances,
when <command>mysqld</command> connects to a cluster
management server, the connection would fail before a node ID
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2005-12-15 11:10:18 UTC (rev 566)
+++ trunk/refman-common/news-5.1.xml 2005-12-15 12:28:44 UTC (rev 567)
@@ -89,6 +89,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Using <literal>ORDER
+ BY <replaceable>primary_key_column</replaceable></literal>
+ when selecting from a table having the primary key on a
+ <literal>VARCHAR</literal> column caused a forced shutdown of
+ the cluster. (Bug #14828, Bug #15240, Bug #15682, Bug #15517)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r567 - trunk/refman-common | jon | 15 Dec |
