svn commit - mysqldoc@docsrva: r9329 - in trunk: dynamic-docs/changelog ndbapi refman-5.0

[jon]

Author: jstephens
Date: 2007-12-14 23:24:10 +0100 (Fri, 14 Dec 2007)
New Revision: 9329

Log:

Documented Cluster bugfixes:

  Bug #21072, Bug #25176, Bug #28445, Bug #29139, Bug #31980,
  Bug #32055, Bug #32275, Bug #32670, Bug #33206, Bug #33168

Added 5.0.56 changelog

Updated NDB Errors



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld-versions.xml
   trunk/dynamic-docs/changelog/mysqld.xml
   trunk/ndbapi/ndb-errors.xml
   trunk/refman-5.0/releasenotes-es-5.0-core.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-14 20:49:21 UTC (rev 9328)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-14 22:24:10 UTC (rev 9329)
Changed blocks: 3, Lines Added: 200, Lines Deleted: 0; 5452 bytes

@@ -9,6 +9,183 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="cluster"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32670"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Under some conditions, performing an <literal>ALTER
+        TABLE</literal> on an <literal>NDBCLUSTER</literal> table
failed
+        with a <errortext>Table is full</errortext> error, even when
+        only 25% of <literal>DataMemory</literal> was in use and the
+        result should have been a table using less memory (for example,
+        changing a <literal>VARCHAR(100)</literal> column to
+        <literal>VARCHAR(80)</literal>).
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="29139"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The error message for <literal>NDB</literal> error code 275
+        (<errortext>Out of transaction records for complete
+        phase</errortext>) was missing.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="28445"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        There was a short interval during the startup process prior to
+        the beginning of heartbeat detection such that, were an API or
+        management node to reboot or a network failure to occur, data
+        nodes could not detect this, with the result that there could be
+        a lingering connection.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="binlog"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32275"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.22-ndb-6.2.10"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When a <command>mysqld</command> acting as a cluster SQL node
+        starts the <literal>NDBCLUSTER</literal> storage engine, there
+        is a delay during which some necessary data structures cannot be
+        initialized until after it has connected to the cluster, and all
+        MySQL Cluster tables should be opened as read-only. This worked
+        correctly when the <literal>NDB</literal> binlog thread was
+        running, but when it was not running, Cluster tables were not
+        opened as read-only even when the data structures had not yet
+        been set up.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="TC"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="33168"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.56"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Incorrectly handled parameters could lead to a crash in the
+        Transaction Coordinator during a node failure, causing other
+        data nodes to fail.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="cluster"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="33206"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.56"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        An improperly reset internal signal was observed as a hang when
+        using events in the <literal>NDB</literal> API but could result
+        in various errors.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
       <manual type="data types"/>
       <manual type="cast"/>
     </tags>

@@ -466,15 +643,21 @@
       <highlight type="importantchange"/>
       <manual type="AUTO_INCREMENT"/>
       <manual type="ndb_autoincrement_prefetch_sz"/>
+      <manual type="INSERT IGNORE"/>
     </tags>
 
     <bugs>
+      <fixes bugid="25176"/>
       <fixes bugid="31956"/>
+      <fixes bugid="32055"/>
     </bugs>
 
     <versions>
+      <version ver="5.0.56"/>
       <version ver="5.1.22-ndb-6.2.10"/>
       <version ver="5.1.22-ndb-6.3.7"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
     </versions>
 
     <message>

@@ -498,6 +681,23 @@
             </para>
           </listitem>
 
+          <listitem>
+            <para>
+              <literal>AUTO_INCREMENT</literal> values were not handled
+              correctly with <literal>INSERT IGNORE</literal>
+              statements.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              After being set,
+              <literal>ndb_autoincrement_prefetch_sz</literal> showed a
+              value of 1, regardless of the value it had actually been
+              set to.
+            </para>
+          </listitem>
+
         </itemizedlist>
         As part of this fix, the behavior of
         <literal>ndb_autoincrement_prefetch_sz</literal> has changed.


Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml	2007-12-14 20:49:21 UTC (rev 9328)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml	2007-12-14 22:24:10 UTC (rev 9329)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 815 bytes

@@ -91,6 +91,7 @@
   <versionentry ver="5.1.3" reldate="29 November 2005"/>
   <versionentry ver="5.1.2" reldate="Not released"/>
   <versionentry ver="5.1.1" reldate="Not released"/>
+  <versionentry ver="5.0.56" versiontag="es" package="mru"  reldate="Not yet
released"/>
   <versionentry ver="5.0.54" versiontag="es" package="mru"  reldate="Not yet
released"/>
   <versionentry ver="5.0.52" versiontag="es" package="mru"  reldate="30 Nov 2007"/>
   <versionentry ver="5.0.51" versiontag="cs" reldate="15 November 2007"/>


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2007-12-14 20:49:21 UTC (rev 9328)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2007-12-14 22:24:10 UTC (rev 9329)
Changed blocks: 3, Lines Added: 36, Lines Deleted: 2; 1634 bytes

@@ -1725,6 +1725,7 @@
     <versions>
       <version ver="5.1.22-ndb-6.2.8"/>
       <version ver="5.1.22-ndb-3.6.3"/>
+      <version ver="6.0.5"/>
     </versions>
 
     <message>

@@ -6775,10 +6776,13 @@
     </bugs>
 
     <versions>
+      <version ver="4.1.22"/>
+      <version ver="5.0.30"/>
       <version ver="5.0.33"/>
+      <version ver="5.0.56"/>
       <version ver="5.1.13"/>
-      <version ver="5.0.30"/>
-      <version ver="4.1.22"/>
+      <version ver="5.1.23"/>
+      <version ver="6.0.5"/>
     </versions>
 
     <message>

@@ -6791,6 +6795,36 @@
 
     </message>
 
+    <message ver="5.0.56">
+
+      <para>
+        When inserting a row into an <literal>NDB</literal> table with a
+        duplicate value for a non-primary unique key, the error issued
+        would reference the wrong key.
+      </para>
+
+      <para>
+        This improves on an initial fix for this issue made in MySQL
+        5.0.30 and MySQL 5.0.33
+      </para>
+
+    </message>
+
+    <message ver="5.1.23">
+
+      <para>
+        When inserting a row into an <literal>NDB</literal> table with a
+        duplicate value for a non-primary unique key, the error issued
+        would reference the wrong key.
+      </para>
+
+      <para>
+        This improves on an initial fix for this issue made in MySQL
+        5.1.13.
+      </para>
+
+    </message>
+
   </logentry>
 
   <logentry entrytype="bug">


Modified: trunk/ndbapi/ndb-errors.xml
===================================================================
--- trunk/ndbapi/ndb-errors.xml	2007-12-14 20:49:21 UTC (rev 9328)
+++ trunk/ndbapi/ndb-errors.xml	2007-12-14 22:24:10 UTC (rev 9329)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 747 bytes

@@ -1468,7 +1468,8 @@
                 <entry><errorcode>275</errorcode></entry>
                 <entry><errorname>DMEC</errorname></entry>
                 <entry><errortype>TR</errortype></entry>
-                <entry><errortext>275</errortext></entry>
+                <entry><errortext>Out of transaction records for complete
phase (increase
+                  MaxNoOfConcurrentTransactions)</errortext></entry>
               </row>
               <row>
                 <entry><errorcode>279</errorcode></entry>


Modified: trunk/refman-5.0/releasenotes-es-5.0-core.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0-core.xml	2007-12-14 20:49:21 UTC (rev 9328)
+++ trunk/refman-5.0/releasenotes-es-5.0-core.xml	2007-12-14 22:24:10 UTC (rev 9329)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 0; 1245 bytes

@@ -38,6 +38,25 @@
     <filename>refman-common</filename> directory.
   </remark>
 
+  <section id="releasenotes-es-5-0-56">
+
+    <title condition="dynamic:changelog:vertitle" role="5.0.56:mysqld:all"/>
+
+    <para>
+      This section documents all changes and bugfixes that have been
+      applied since the last MySQL Enterprise Server release (5.0.54).
+      If you would like to receive more fine-grained and personalized
+      <emphasis>update alerts</emphasis> about fixes that are relevant
+      to the version and features you use, please consider subscribing
+      to <emphasis>MySQL Enterprise</emphasis> (a commercial MySQL
+      offering). For more details please see
+      <ulink url="&base-url-enterprise;advisors.html"/>.
+    </para>
+
+    <para condition="dynamic:changelog:entrylist" role="5.0.56:mysqld:all"/>
+
+  </section>
+
   <section id="releasenotes-es-5-0-54">
 
     <title condition="dynamic:changelog:vertitle" role="5.0.54:mysqld:all"/>