Author: jstephens
Date: 2005-12-14 19:33:47 +0100 (Wed, 14 Dec 2005)
New Revision: 563
Log:
Documented Cluster bugfixes:
- 15240/15682, 15215, 15828 (5.0)
- 15887 (4.1/5.0)
Updated Cluster Limitations regarding transaction isolation behaviour when
selecting from BLOB/TEXT/VARCHAR. (Fix for Bug#15282 - RefMan-4.1/5.0/5.1)
Modified:
trunk/refman-4.1/ndbcluster.xml
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.1/ndbcluster.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2005-12-14 18:11:00 UTC (rev 562)
+++ trunk/refman-4.1/ndbcluster.xml 2005-12-14 18:33:47 UTC (rev 563)
@@ -8803,10 +8803,41 @@
<listitem>
<para>
- There is no partial rollback of transactions. A duplicate
- key or similar error will result in a rollback of the
- entire transaction.
+ <emphasis role="bold">Transaction Handling</emphasis>:
</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> supports only the
+ <literal>READ_COMMITTED</literal> transaction
+ isolation level.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is no partial rollback of transactions. A
+ duplicate key or similar error will result in a
+ rollback of the entire transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Important</emphasis>: If a
+ <literal>SELECT</literal> from a Cluster table
+ includes a <literal>BLOB</literal>,
+ <literal>TEXT</literal>, or <literal>VARCHAR</literal>
+ column, then the <literal>READ_COMMITTED</literal>
+ transaction isolation level is converted to a read
+ with read lock. This is done in order to guarantee
+ consistency, due to the fact that parts of the values
+ stored in columns of these types are actually read
+ from a separate table.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
<listitem>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2005-12-14 18:11:00 UTC (rev 562)
+++ trunk/refman-5.0/ndbcluster.xml 2005-12-14 18:33:47 UTC (rev 563)
@@ -3999,7 +3999,7 @@
When a transaction is committed, it is committed in main
memory in all nodes on which the data is mirrored.
However, transaction log records are not flushed to disk
- as part of the commit. The reasoning behing this behavior
+ as part of the commit. The reasoning behind this behavior
is that having the transaction safely committed on at
least two autonomous host machines should meet reasonable
standards for durability.
@@ -8779,10 +8779,42 @@
<listitem>
<para>
- There is no partial rollback of transactions. A duplicate
- key or similar error will result in a rollback of the
- entire transaction.
+ <emphasis role="bold">Transaction Handling</emphasis>:
</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> supports only the
+ <literal>READ_COMMITTED</literal> transaction
+ isolation level.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is no partial rollback of transactions. A
+ duplicate key or similar error will result in a
+ rollback of the entire transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Important</emphasis>: If a
+ <literal>SELECT</literal> from a Cluster table
+ includes a <literal>BLOB</literal>,
+ <literal>TEXT</literal>, or <literal>VARCHAR</literal>
+ column, then the <literal>READ_COMMITTED</literal>
+ transaction isolation level is converted to a read
+ with read lock. This is done in order to guarantee
+ consistency, due to the fact that parts of the values
+ stored in columns of these types are actually read
+ from a separate table.
+ </para>
+ </listitem>
+ </itemizedlist>
+
</listitem>
<listitem>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2005-12-14 18:11:00 UTC (rev 562)
+++ trunk/refman-5.1/ndbcluster.xml 2005-12-14 18:33:47 UTC (rev 563)
@@ -8778,10 +8778,41 @@
<listitem>
<para>
- There is no partial rollback of transactions. A duplicate
- key or similar error will result in a rollback of the
- entire transaction.
+ <emphasis role="bold">Transaction Handling</emphasis>:
</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> supports only the
+ <literal>READ_COMMITTED</literal> transaction
+ isolation level.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is no partial rollback of transactions. A
+ duplicate key or similar error will result in a
+ rollback of the entire transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Important</emphasis>: If a
+ <literal>SELECT</literal> from a Cluster table
+ includes a <literal>BLOB</literal>,
+ <literal>TEXT</literal>, or <literal>VARCHAR</literal>
+ column, then the <literal>READ_COMMITTED</literal>
+ transaction isolation level is converted to a read
+ with read lock. This is done in order to guarantee
+ consistency, due to the fact that parts of the values
+ stored in columns of these types are actually read
+ from a separate table.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
<listitem>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-12-14 18:11:00 UTC (rev 562)
+++ trunk/refman-common/news-4.1.xml 2005-12-14 18:33:47 UTC (rev 563)
@@ -179,6 +179,14 @@
</para>
<itemizedlist>
+
+ <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>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-12-14 18:11:00 UTC (rev 562)
+++ trunk/refman-common/news-5.0.xml 2005-12-14 18:33:47 UTC (rev 563)
@@ -205,9 +205,27 @@
</para>
<itemizedlist>
-
+
<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>
+ <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)
+ </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)
@@ -278,6 +296,15 @@
</para>
<itemizedlist>
+
+ <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
+ could be allocated. (Bug #15215)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r563 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | jon | 14 Dec |
