Author: jstephens
Date: 2006-04-08 07:21:15 +0200 (Sat, 08 Apr 2006)
New Revision: 1762
Log:
Node stop/start and transaction handling. (Jonas)
Fixes Docs Bug #18746.
Modified:
trunk/refman-4.1/ndbcluster.xml
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.1/ndbcluster.xml
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2006-04-08 04:57:10 UTC (rev 1761)
+++ trunk/refman-4.1/ndbcluster.xml 2006-04-08 05:21:15 UTC (rev 1762)
@@ -9460,6 +9460,43 @@
</itemizedlist>
</listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Node Start, Stop, or
+ Restart:</emphasis>: Starting, stopping, or
+ restarting a node may give rise to temporary errors
+ causing some transactions to fail. These include the
+ following cases:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ When first starting a node, it is possible that
+ you may see Error 1204 <errortext>Temporary
+ failure, distribution changed</errortext> and
+ similar temporary errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The stopping or failure of any data node can
+ result in a number of different node failure
+ errors. (However, there should be no aborted
+ transactions when performing a planned shutdown of
+ the cluster.)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In either of these cases, any errors that are
+ generated must be handled within the application. This
+ should be done by retrying the transaction.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-04-08 04:57:10 UTC (rev 1761)
+++ trunk/refman-5.0/ndbcluster.xml 2006-04-08 05:21:15 UTC (rev 1762)
@@ -9377,70 +9377,39 @@
<listitem>
<para>
- As noted elsewhere in this chapter, MySQL Cluster does
- not handle large transactions well; it is better to
- perform a number of small transactions with a few
- operations each than to attempt a single large
- transaction containing a great many operations.
+ <emphasis role="bold">Node Start, Stop, or
+ Restart:</emphasis>: Starting, stopping, or
+ restarting a node may give rise to temporary errors
+ causing some transactions to fail. These include the
+ following cases:
</para>
- <para>
- Among other considerations, large transactions require
- very large amounts of memory. Because of this, the
- transactional behaviour of a number of MySQL
- statements is effected as described in the following
- list:
- </para>
-
<itemizedlist>
<listitem>
<para>
- <literal>TRUNCATE</literal> is not transactional
- when used on <literal>NDB</literal> tables. If a
- <literal>TRUNCATE</literal> fails to empty the
- table, then it is re-run until it is successful.
- </para>
+ When first starting a node, it is possible that
+ you may see Error 1204 <errortext>Temporary
+ failure, distribution changed</errortext> and
+ similar temporary errors.
+ </para>
</listitem>
<listitem>
<para>
- <literal>DELETE FROM</literal> (even with no
- <literal>WHERE</literal> clause)
- <emphasis>is</emphasis> transactional. For tables
- containing a great many rows, you may find that
- performance is improved by using several
- <literal>DELETE FROM ... LIMIT ...</literal>
- statements to <quote>chunk</quote> the delete
- operation. If the objective is to empty the table,
- then you may wish to use
- <literal>TRUNCATE</literal> instead.
+ The stopping or failure of any data node can
+ result in a number of different node failure
+ errors. (However, there should be no aborted
+ transactions when performing a planned shutdown of
+ the cluster.)
</para>
</listitem>
-
- <listitem>
- <para>
- <literal>LOAD DATA INFILE</literal> is not
- transactional. During such an operation the
- <literal>NDB</literal> engine can and does commit
- at will.
- </para>
-
- <para>
- <literal>LOAD DATA FROM MASTER</literal> is not
- supported in MySQL Cluster.
- </para>
- </listitem>
-
- <listitem>
- <para>
- When copying a table as part of an <literal>ALTER
- TABLE</literal>, the creation of the copy is
- non-transactional. (In any case, this operation is
- rolled back when the copy is deleted.)
- </para>
- </listitem>
</itemizedlist>
+ <para>
+ In either of these cases, any errors that are
+ generated must be handled within the application. This
+ should be done by retrying the transaction.
+ </para>
</listitem>
</itemizedlist>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-04-08 04:57:10 UTC (rev 1761)
+++ trunk/refman-5.1/ndbcluster.xml 2006-04-08 05:21:15 UTC (rev 1762)
@@ -11528,6 +11528,43 @@
</itemizedlist>
</listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Node Start, Stop, or
+ Restart:</emphasis>: Starting, stopping, or
+ restarting a node may give rise to temporary errors
+ causing some transactions to fail. These include the
+ following cases:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ When first starting a node, it is possible that
+ you may see Error 1204 <errortext>Temporary
+ failure, distribution changed</errortext> and
+ similar temporary errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The stopping or failure of any data node can
+ result in a number of different node failure
+ errors. (However, there should be no aborted
+ transactions when performing a planned shutdown of
+ the cluster.)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In either of these cases, any errors that are
+ generated must be handled within the application. This
+ should be done by retrying the transaction.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1762 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 8 Apr |
