List:Commits« Previous MessageNext Message »
From:jon Date:May 15 2007 7:00am
Subject:svn commit - mysqldoc@docsrva: r6458 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-05-15 09:00:56 +0200 (Tue, 15 May 2007)
New Revision: 6458

Log:

Documented Cluster bugfixes:

  Bug #26675, Bug #27202, Bug #27292, 
  Bug #27437, Bug #27942, Bug #28276



Modified:
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-05-15 06:15:46 UTC (rev 6457)
+++ trunk/refman-5.1/news-5.1.xml	2007-05-15 07:00:56 UTC (rev 6458)
Changed blocks: 3, Lines Added: 79, Lines Deleted: 0; 3293 bytes

@@ -84,6 +84,65 @@
       
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: Multiple operations involving
+          deletes followed by reads were not handled correctly. (Bug
+          #28276)
+        </para>
+        <note>
+        <para>
+          This issue could also affect MySQL Cluster Replication.
+        </para>
+        </note>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Disk Data): Extremely large
+          inserts into Disk Data tables could lead to data node failure
+          in some circumstances. (Bug #27942)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Repeated insertion of data
+          generated by <command>mysqldump</command> into
+          <literal>NDB</literal> tables could eventually lead to failure
+          of the cluster. (Bug #27437)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Restarting a data node caused
+          SQL nodes to log repeatedly and unnecessarily the status of
+          the event buffer. (Bug #27292)
+        </para>
+        
+        <para>
+          (This issue was known to occur in MySQL 5.1.16 and later
+          only.)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_mgmd</command>
+          failed silently when the cluster configuration file contained
+          invalid <literal>[TCP]</literal> entries. (Bug #27207)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>:
+          <literal>ndb_connectstring</literal> did not appear in the
+          output of <literal>SHOW VARIABLES</literal>. (Bug #26675)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal> (APIs): In a multi-operation
           transaction, a delete operation followed by the insertion of
           an implicit <literal>NULL</literal> failed to overwrite an

@@ -4581,6 +4640,18 @@
       </para>
 
       <itemizedlist>
+      
+      <listitem>
+        <para>
+          Multiple operations involving deletes followed by reads were
+          not handled correctly. (Bug #28276)
+        </para>
+        <note>
+        <para>
+          This issue could also affect MySQL Cluster Replication.
+        </para>
+        </note>
+      </listitem>
 
         <listitem>
           <para>

@@ -6470,6 +6541,14 @@
       
       <listitem>
         <para>
+          <emphasis role="bold">Disk Data</emphasis>: Extremely large
+          inserts into Disk Data tables could lead to data node failure
+          in some circumstances. (Bug #27942)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           <emphasis role="bold">Cluster APIs</emphasis>: In a
           multi-operation transaction, a delete operation followed by
           the insertion of an implicit <literal>NULL</literal> failed to


Thread
svn commit - mysqldoc@docsrva: r6458 - trunk/refman-5.1jon15 May