svn commit - mysqldoc@docsrva: r12116 - in trunk: dynamic-docs/changelog ndbapi refman-5.1

[jon]

Author: jstephens
Date: 2008-10-22 00:59:00 +0200 (Wed, 22 Oct 2008)
New Revision: 12116

Log:

Documented Cluster Bugfixes:
  Bug #32656
  Bug #28496
  Bug #34638

Updated 5.1 Cluster Limitations

Updated NDB Error Codes



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/ndbapi/ndb-error-codes.xml
   trunk/refman-5.1/mysql-cluster-limitations.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-10-21 21:28:46 UTC (rev 12115)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-10-21 22:59:00 UTC (rev 12116)
Changed blocks: 1, Lines Added: 91, Lines Deleted: 0; 2462 bytes

@@ -9,6 +9,97 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="diskdata"/>
+      <manual type="O_SYNC"/>
+      <manual type="O_DIRECT"/>
+      <manual type="Solaris"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="34638"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28-ndb-6.2.17"/>
+      <version ver="5.1.28-ndb-6.3.19"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal>O_SYNC</literal> was incorrectly disabled on platforms
+        that do not support <literal>O_DIRECT</literal>. This issue was
+        noted on Solaris but could have affected other platforms not
+        having <literal>O_DIRECT</literal> capability.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="error messages"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="28496"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28-ndb-6.2.17"/>
+      <version ver="5.1.28-ndb-6.3.19"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Error messages for <literal>NDBCLUSTER</literal> error codes
+        1224 and 1227 were missing.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="transactions"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32656"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28-ndb-6.3.19"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A duplicate key error raised when inserting into an
+        <literal>NDBCLUSTER</literal> table caused the current
+        transaction to abort, after which any SQL statement other than a
+        <literal>ROLLBACK</literal> failed. With this fix, the
+        <literal>NDBCLUSTER</literal> storage engine now supports
+        rollback of individual statements in such cases, and it is no
+        longer necessary to issue an explicit
+        <literal>ROLLBACK</literal> and then retry the entire
+        transaction.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
       <highlight type="importantchange"/>
       <manual type="Falcon"/>
       <manual type="INFORMATION_SCHEMA"/>


Modified: trunk/ndbapi/ndb-error-codes.xml
===================================================================
--- trunk/ndbapi/ndb-error-codes.xml	2008-10-21 21:28:46 UTC (rev 12115)
+++ trunk/ndbapi/ndb-error-codes.xml	2008-10-21 22:59:00 UTC (rev 12116)
Changed blocks: 5, Lines Added: 26, Lines Deleted: 1; 3055 bytes

@@ -2112,6 +2112,12 @@
             <entry><errortext>Unsupported character set in table or
index</errortext></entry>
           </row>
           <row>
+            <entry><errorcode>1224</errorcode></entry>
+           
<entry><errorname>HA_WRONG_CREATE_OPTION</errorname></entry>
+            <entry><errortype>SE</errortype></entry>
+            <entry><errortext>Too many
fragments</errortext></entry>
+          </row>
+          <row>
             <entry><errorcode>1225</errorcode></entry>
             <entry><errorname>DMEC</errorname></entry>
             <entry><errortype>SE</errortype></entry>

@@ -2124,6 +2130,12 @@
             <entry><errortext>Table is being
dropped</errortext></entry>
           </row>
           <row>
+            <entry><errorcode>1227</errorcode></entry>
+           
<entry><errorname>HA_WRONG_CREATE_OPTION</errorname></entry>
+            <entry><errortype>SE</errortype></entry>
+            <entry><errortext>Invalid schema
version</errortext></entry>
+          </row>
+          <row>
             <entry><errorcode>1228</errorcode></entry>
             <entry><errorname>DMEC</errorname></entry>
             <entry><errortype>SE</errortype></entry>

@@ -2703,6 +2715,13 @@
               transaction</errortext></entry>
           </row>
           <row>
+            <entry><errorcode>291</errorcode></entry>
+            <entry><errorname>DMEC</errorname></entry>
+            <entry><errortype>TR</errortype></entry>
+            <entry><errortext>Out of scanfrag records in TC (increase
+              MaxNoOfLocalScans)</errortext></entry>
+          </row>
+          <row>
             <entry><errorcode>784</errorcode></entry>
             <entry><errorname>DMEC</errorname></entry>
             <entry><errortype>TR</errortype></entry>

@@ -2873,6 +2892,12 @@
             <entry><errortext>Simple/dirty read failed due to node
failure</errortext></entry>
           </row>
           <row>
+            <entry><errorcode>786</errorcode></entry>
+            <entry><errorname>DMEC</errorname></entry>
+            <entry><errortype>NR</errortype></entry>
+            <entry><errortext>Schema transaction aborted due to
node-failure</errortext></entry>
+          </row>
+          <row>
             <entry><errorcode>1405</errorcode></entry>
             <entry><errorname>DMEC</errorname></entry>
             <entry><errortype>NR</errortype></entry>

@@ -3295,7 +3320,7 @@
             <entry><errortext>Corrupt key in TC, unable to
xfrm</errortext></entry>
           </row>
           <row>
-            <entry><errorcode>291</errorcode></entry>
+            <entry><errorcode>293</errorcode></entry>
             <entry><errorname>DMEC</errorname></entry>
             <entry><errortype>IE</errortype></entry>
             <entry><errortext>Inconsistent trigger state in TC
block</errortext></entry>


Modified: trunk/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations.xml	2008-10-21 21:28:46 UTC (rev 12115)
+++ trunk/refman-5.1/mysql-cluster-limitations.xml	2008-10-21 22:59:00 UTC (rev 12116)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 26; 2921 bytes

@@ -631,31 +631,6 @@
         <listitem>
           <formalpara>
 
-            <title>Rollbacks</title>
-
-            <para>
-              There are no partial transactions, and no partial
-              rollbacks of transactions. A duplicate key or similar
-              error aborts the entire transaction, and subsequent
-              statements raise <errortext>ERROR 1296 (HY000): Got error
-              4350 'Transaction already aborted' from
-              NDBCLUSTER</errortext>. In such cases, you must issue an
-              explicit <literal>ROLLBACK</literal> and retry the entire
-              transaction.
-            </para>
-
-          </formalpara>
-
-          <para>
-            This behavior differs from that of other transactional
-            storage engines such as <literal>InnoDB</literal> that may
-            roll back individual statements.
-          </para>
-        </listitem>
-
-        <listitem>
-          <formalpara>
-
             <title>Transactions and memory usage</title>
 
             <indexterm>

@@ -1569,7 +1544,8 @@
 
   <section id="mysql-cluster-limitations-resolved">
 
-    <title>Previous MySQL Cluster Issues Resolved in MySQL
&current-series;</title>
+    <title>Previous MySQL Cluster Issues Resolved in MySQL 5.1 and MySQL Cluster
+      NDB 6.x</title>
 
     <indexterm>
       <primary>MySQL Cluster limitations</primary>

@@ -1938,6 +1914,36 @@
           </formalpara>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title>Rollbacks</title>
+
+            <para>
+              Prior to MySQL Cluster NDB 6.3.19, the
+              <literal>NDBCLUSTER</literal> storage engine did not
+              support partial transactions or partial rollbacks of
+              transactions. A duplicate key or similar error aborted the
+              entire transaction, and subsequent statements raised
+              <errortext>ERROR 1296 (HY000): Got error 4350 'Transaction
+              already aborted' from NDBCLUSTER</errortext>. In such
+              cases, it was necessary to issue an explicit
+              <literal>ROLLBACK</literal> and retry the entire
+              transaction.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Beginning with MySQL Cluster NDB 6.3.19, this limitation has
+            been removed, and the behavior of
+            <literal>NDBCLUSTER</literal> is now in line with that of
+            other transactional storage engines such as
+            <literal>InnoDB</literal> which can roll back individual
+            statements. (Bug #32656)
+          </para>
+        </listitem>
+
       </itemizedlist>
     </para>